Measuring video viewing

ABSTRACT

System and methods for determining second-by-second viewing activity and viewing metrics associated with video assets output by a plurality of video-viewing devices. The viewing activity may include a viewing mode by which one or more video viewing devices output a segment of a video asset. The viewing metrics may include a viewing count for a segment of the video asset that is associated with a viewing mode by which the one or more video viewing devices output the video segment. These metrics provide detailed information on customer viewing behavior which can be used to drive business decisions for service providers, advertisers, and content producers.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/567,073, filed on Aug. 5, 2012, which is a continuation-in-part ofU.S. patent application Ser. No. 12/981,301, filed on Dec. 29, 2010 (nowU.S. Pat. No. 8,365,212). All of the above priority applications arehereby incorporated by reference in their entireties.

This application is also related to the co-pending application U.S.application Ser. No. 13/052,026 filed on Mar. 18, 2011 entitled “SYSTEMAND METHOD FOR MEASURING TELEVISION ADVERTISING AND PROGRAM VIEWING AT ASECOND-BY-SECOND LEVEL AND FOR MEASURING EFFECTIVENESS OF TARGETEDADVERTISING” by the present inventor which is incorporated by referencein its entirety but is not admitted to be prior art.

This application is also related to the co-pending application U.S.application Ser. No. 13/360,704 filed on Jan. 28, 2012 entitled “SYSTEMAND METHOD FOR MEASURING LONGITUDINAL VIDEO ASSET VIEWING AT ASECOND-BY-SECOND LEVEL TO UNDERSTAND BEHAVIOR OF VIEWERS AS THEYINTERACT WITH VIDEO ASSET VIEWING DEVICES THAT ACCESS A COMPUTER SYSTEMTHROUGH A NETWORK” by the present inventor which is incorporated byreference in its entirety but is not admitted to be prior art.

PROGRAM LISTING

This patent submission contains one (1) program listing as shown in thetable below.

The following program listing is incorporated in this Specification byreference.

Name of the ASCII Text file Date of Creation Size in bytes 1.Orlowski-Measuring-Video-Program- 08/05/2021 385,475Viewing-Source-Code.txt

Note: Variable names used in program correspond to specification, butmay not match exactly.

BACKGROUND—PRIOR ART

The following is a tabulation of some prior art that presently appearsrelevant:

U.S. Patents Pat. No. Class Issue Date Patentee 7,383,243 725/2 Jun. 3,2008 Conkwright, et al. 7,590,993 725/35 Sep. 15, 2009 Hendricks, et al.

U.S. Patent Application Publications Publication Kind Publication NumberCode Class Date Applicant 20070074258 A1 725/105 Mar. 29, 2007 Wood;Catherine Alexandra 2010/0145791 A1 705/14.41 Jun. 10, 2010 Canning;Brian P. 20060168609 A1 725/9 Jul. 27, 2006 Chen; Michael A.

BACKGROUND INFORMATION General Statement of Problem

With the ever increasing number of consumer choices for televisionviewing, it is important for advertisers, content producers, and serviceproviders such as cable television and satellite television and internetprotocol television companies to be able to accurately measure audienceviewership at various levels including video program, video programairing, video program airing segment, demographic group, geographicgroup, and viewing device type. The device type must allow measurementacross various platforms such as set top box, PC, tablet, smart phone,IP TV, etc. and various viewing device characteristics. Each of theseviewing measures must be available for various forms of video viewingincluding Linear TV, Digital Video Recording and Playback, and Video onDemand. Traditional methods of measuring television viewership do notprovide one-second level viewing information for Linear TV, DigitalVideo Recording and Playback, and Video on Demand even though this couldbe extremely helpful to advertisers, content producers, and contentproviders.

Advertising Industry Problem

Producing television ads and purchasing ad time to run those ads isexpensive. Ideally, the advertising purchased with those dollars can becorrelated with ad impressions. Unfortunately, measuring ad impressionsor ad viewership is very difficult, especially when there are hundredsof channels and many of them are lightly viewed. The problem ismagnified by channel-surfing and by multi-screen activity wherein oneperson may use personal viewing devices, traditional cable or satellitetelevision, and perhaps computer based viewing. While traditional surveytechniques provide audience measures for popular channels, they areinadequate for lightly-viewed channels, which can be up to 80% of thechannels. In today's competitive media environment, televisionadvertisers need accurate and detailed viewing information for programs,for program airings, and for segments in program airings with suitablebreakouts for demographic, geographic and device characteristic so thatthey can measure the effectiveness of their advertising.

In a Linear viewing environment, advertisers need detailed informationon viewing of the ads that they pay to air. When a program is airedmultiple times, viewing will vary depending on various factors such astime of day when the program aired. Advertisers need to understandviewership of each program airing and of the program as a whole acrossall airings in order to make effective ad placement decisions.Additionally advertisers need insight into the demographiccharacteristics of their viewers, their geographic location, and thetype of device used to view the content.

In a Digital Video Recording environment advertising effectiveness canbe measured by observing viewer response to ads; do viewers view the adsor do they fast forward or skip past them? Advertisers need tounderstand whether or not their ads are being seen by viewers. In thecase of DVR, the advertisers need measurements on how many viewers saweach ad within so many hours of the linear airing or the DVR recording.Furthermore, they need to understand which viewers view the ads andwhich viewers skip the ads or fast forward through the ads.

Advertisers need to be able to measure ad impressions in both a linearviewing environment and in DVR and VOD environments. Additionally, theyneed second-by-second measurements to determine channel surfing activityduring ads. Such measurement will allow advertisers to measure theeffectiveness of their ads.

I have not found any patents or patent applications that teach how touse set top box data to efficiently analyze second-by-second viewershipof advertising to produce the detailed information that advertisersneed.

Television Network Problem

Television networks need to create an appealing programming schedulewith content that the viewers are interested in viewing. It is difficultfor television networks to get accurate audience feedback, particularlyfor lightly viewed networks. They need to be able to measure viewingpatterns for each show. They also need to understand viewership acrossviewing platforms or viewing devices and to understand viewership in amulti-screen world. The diversity of the viewing audience makes thismore difficult to measure. Traditional measurement tools do not providethe detailed information needed to help television networks understandhow viewers are responding to the content. The result is that televisionnetworks may develop programming schedules that do not appeal to theaudience. This is wasteful.

Content Producers Problem

Producing television content is often expensive. It is difficult for thecontent producers to get accurate audience feedback. Additionally, thereis not one audience, but many audiences, because of the wide variety ofviewer interests. Furthermore, any person may view content on multipledevices. The content producers need to tailor the content to theaudience. With the increasing number of viewing choices it is all themore important to be able to accurately measure viewership on diverseplatforms in order to be able to justify advertising fees. Traditionalmeasurement tools do not provide the detailed information needed to helpproducers and writers to understand how viewers are responding to thecontent. The result is that producers may develop content that lacksinterest to the audience. This is wasteful.

Cable Television Industry Problem

In the cable television industry, content providers offer consumershundreds of channels. Cable television companies pay very large amountsof money for content. It is imperative for the cable televisioncompanies to be able to accurately measure audience viewership in orderto understand what value the various programs bring to their customers.They must understand viewership across viewing platforms or viewingdevices; they must understand viewership in a multi-screen world. Also,by understanding the time of day when various programs are viewed, thecable television companies can create more attractive viewing schedulesfor their customers. Additionally, as cable television companies areable to accurately measure audience viewership, they will be able tobetter negotiate with the program providers on the price to be paid forprogramming content and with advertisers on the price to charge forairing advertising.

Satellite Television Industry Problem

The satellite television industry faces the same problems as the cabletelevision industry in regard to understanding what programming theviewers are watching and at what time of day and on what device. Ingeneral they have the same need to understand viewer behavior as do thecable television companies.

Internet Protocol Television Industry Problem

The Internet Protocol television (IP TV) industry faces the sameproblems as the cable television industry in regard to understandingwhat programming the viewers are watching and at what time of day and onwhat device. In general they have the same need to understand viewerbehavior as do the cable television companies.

Need for Information about the Customer

In addition to these issues, cable television companies, satellitetelevision companies, IP TV providers, television content providers,television advertisers, and other interested parties are continuallydesiring to know more about the customers they serve, the patterns ofcustomer interactions, the content customers find interesting or thatkeeps their attention, the ads they view, the time of day when variousprogram are viewed, how programs compare with one another in keepingviewer interest, and numerous other measures. With the advent ofportable video viewing devices, the need to understand viewer behavioris even more important.

Fortunately, currently available technology enables the collection ofraw data that, with proper analysis, can begin to answer many of thesequestions, and even do so with great specificity.

We will now look at some sources of raw data in the television industry.

Video Viewing Activity Data Sources

Since my original United States patent application having applicationSer. No. 12/981,301 filed on Dec. 29, 2010, the industry has continuedto mature. In the past it was common to refer to this data as ChannelTuning activity. While that term is accurate, in this specification Iwill often use the more general term Video Viewing Activity to reflectthat I am analyzing video viewing activity which may include linearviewing, DVR playback, and VOD viewing.

Within the video viewing space there are collection systems in place forcollecting linear viewing activity, and for collecting DVR recording andplayback activity, and for collecting VOD playback activity. Suchcollection systems include switched digital video collection systems,set top box data collection systems, IP Television collection systems,EBIF agents, etc. Many such applications are now well established in theindustry; others are continually being developed. Such data collectionis beyond the scope of this patent application. It will suffice to knowthat the needed video viewing activity is available.

Video Program Schedule Data Sources

As with the collection of video viewing activity data, the availabilityof program schedule data is rapidly expanding. There are variousindustry standards in this area and new standards are being developed.For purposes of media measurement, these systems can provide thedetailed information about the video programs, program schedulesidentifying when they aired in the various markets, how the videoprograms can be segmented, what video asset played in each segment, andwhether the segment allowed static or dynamic content, and other helpfulinformation.

Media Measurement Data Model

This specification assumes that viewer interaction data can be deliveredin a format that allows my Measurement Engine 200 to ingest it. I willrefer to this format as a Media Measurement Data Model or MMDM. Oncedata is available in this format, it can be readily processed usingalgorithms which I will teach about in this specification.

As to loading the viewing data to this Media Measurement data model,there are any number of methods that can be used to do that. The loadingof the Media Measurement data model is beyond the scope of this patentapplication.

File Transfer to Receive the Data

Once the Media Measurement Data Model has been populated with thenecessary data, it is a simple task to make that data available to aMeasurement Engine whether through SQL queries, data base extracts, XMLmessages, or any other computer readable format.

Encryption may be applied for data security purposes. Compression may beapplied to reduce data transfer volumes.

Additionally, once the data is enriched, key identifiers can be hashedor encrypted or de-identified to protect the identity of the viewer.

Existing Tools for Data Analysis

We have seen by way of background that video viewing activity data andprogram schedule data is readily available. Regarding tools for usingthis data to analyze detailed viewing patterns, I am not aware of anyvendor solutions or patents that load second-by-second channel tuningdata or video asset viewing device usage data into a Data Structure inthe memory of a computer to identify second-by-second video viewingactivity identifying the video program identifier, the video programairing identifier, the viewing session identifier, the demographicidentifier of the viewer, the geographic location of the viewer, or thedevice type used by the viewer to then calculate viewing activity for aprogram or a part of a program to produce viewing metrics.

Relevant Patents

The patents and patent applications identified below are only mildlyrelevant. I include them here to acknowledge that others have taughtabout using set-top box data, but none have used it as I teach in thisapplication and none have been able to produce the detailed metrics thatI have identified herein.

Examples Include:

Conkwright, et al. in U.S. Pat. No. 7,383,243 issued Jun. 3, 2008teaches about collecting set-top box data for the purpose of predictingwhat consumers will do, not for the purpose of understanding actualviewer behavior. It appears that he does not teach the loading of a datastructure containing buckets representing individual units of time toanalyze viewing behavior.

Hendricks, et al. in U.S. Pat. No. 7,590,993 Method and apparatus forgathering programs watched data issued Sep. 15, 2009 teaches aboutcollecting tuning data from the set-top box and combining that withother data in a data base to determine the types of programming the STBtunes to. It appears that he does not teach the loading of a datastructure containing buckets representing individual units of time toanalyze viewing behavior.

Relevant Patent Applications

Wood; Catherine Alexandra in U.S. Patent Application 20070074258 datedMar. 29, 2007 teaches about collecting subscriber activity data, such aschannel changes generated by the subscriber while watching video or TVin an IPTV system. It appears that she does not teach the loading of adata structure containing buckets representing individual units of timeto analyze viewing behavior. It appears instead that she teaches loadingthe channel tuning data to a relational data base and then performingvarious SQL based queries against that data base.

Eldering; Charles A.; et al. in U.S. Patent Application 20080127252dated May 29, 2008 teaches about targeted advertising. He notes that SDVsystems have the ability to provide viewership counts. It appears thathe does not teach the loading of a data structure containing bucketsrepresenting individual units of time to analyze viewing behavior.

Allegrezza; Fred J.; et al. in U.S. Patent Application 20090077577 datedMar. 19, 2009 teaches about aggregating information obtained from themessages to generate channel viewership information identifying a numberof subscribers tuned to each broadcast channel over a period of time,but it appears to be based simply on tune-in activity. It appears thathe does not teach the loading of a data structure containing bucketsrepresenting individual units of time to analyze viewing behavior.

Bou-Abboud; Claude H. in U.S. Patent Application 20070214483 dated Sep.13, 2007 teach about a tool for predicting capacity demands on anelectronic system. It appears that they do not teach the loading of adata structure containing buckets representing individual units of timeto analyze viewing behavior.

Canning; Brian P.; et al. in U.S. Patent Application 20100145791 datedJun. 10, 2010 teach about storing data in multiple shards and supportingqueries against the data. It appears that he does not teach the loadingof a data structure containing buckets representing individual units oftime to analyze viewing behavior.

Summary of Short-Comings in Data Analysis Tools

In general, a short-coming of these methods is that the foundation is anon-procedural language (SQL) used in conjunction with a relational database which together do not have the detailed processing capabilityrequired to perform complex analytics. In such an environment, in orderto capture the richness of certain aspects of the channel tuning data,one would have to explode the data out into individual rows with one rowfor each second of viewer activity. In such an environment, this isextremely expensive because adding a primary key to each data recordsimply to record the second (time) multiplies the volume of data manytimes over because the size of the primary key requires much morestorage space than the data being recorded. Thus we see that using anon-procedural language (SQL) in conjunction with a relational data baseis very inefficient and requires extremely powerful data base servers toanalyze this data. In contrast I am able to produce these complexanalytics on a simple personal computer.

As a result of not being able to perform the detailed analyticsrequired, the behavioral and device usage information contained in thedata remains hidden from interested parties.

SUMMARY

In accordance with one embodiment, I disclose a computer-implementedmethod of using video program viewer interaction data that has beenloaded to a media measurement database as input to a measurement enginewhich then calculates Linear, DVR, and VOD asset viewing activity atthree levels: (a) Video Program, (b) Video Program Airing, (c) VideoProgram Airing Segment, where each level provides summary metrics forgroupings of Demographic, Geographic, and/or Device Characteristic, andalso second-by-second viewing metrics, including counting advertisingimpressions, within the Demographic, Geographic, Device groupings.System also accounts for reduced value of ad viewing when viewer isusing trick plays or when viewer delays viewing recorded content.Together these metrics provide detailed information on customer viewingbehavior which can be used to drive business decisions for serviceproviders, advertisers, and content producers. Additionally, a viewinghistogram analysis is produced.

Advantages

By creating Linear, DVR, and VOD asset viewing activity at three levels:(a) Video Program, (b) Video Program Airing, (c) Video Program AiringSegment, where each level provides summary metrics for groupings ofDemographic Code, Geographic, and/or Device Characteristic, and alsosecond-by-second viewing metrics within the Demographic, Geographic,Device groupings I am able to provide detailed viewing metrics thatcould not be produced previously. Existing analysis techniques simply donot allow the creation of the detailed viewing metrics which I have beenable to produce. These metrics will allow service providers,advertisers, and content producers to make intelligent businessdecisions benefiting both themselves and their customers.

In my co-pending United States patent application having applicationSer. No. 12/981,301 filed on Dec. 29, 2010 entitled “SYSTEM AND METHODFOR ANALYZING HUMAN INTERACTION WITH ELECTRONIC DEVICES THAT ACCESS ACOMPUTER SYSTEM THROUGH A NETWORK”, which is incorporated in itsentirety but is not admitted to be prior art, and in my co-pendingUnited States patent application having application Ser. No. 13/052,026filed on Mar. 18, 2011 entitled “SYSTEM AND METHOD FOR MEASURINGTELEVISION ADVERTISING AND PROGRAM VIEWING AT A SECOND-BY-SECOND LEVELAND FOR MEASURING EFFECTIVENESS OF TARGETED ADVERTISING”, which isincorporated in its entirety but is not admitted to be prior art, Itaught populating a Data Structure with identifying information anddevice usage information such as channel tuning data to create afoundation upon which a comprehensive set of metrics can be produced. Inthose applications I also taught loading the tuning data on asecond-by-second basis into buckets in a data structure for analytics.

In my co-pending United States patent application having applicationSer. No. 13/360,704 filed on Jan. 28, 2012 entitled “SYSTEM AND METHODFOR MEASURING LONGITUDINAL VIDEO ASSET VIEWING AT A SECOND-BY-SECONDLEVEL TO UNDERSTAND BEHAVIOR OF VIEWERS AS THEY INTERACT WITH VIDEOASSET VIEWING DEVICES THAT ACCESS A COMPUTER SYSTEM THROUGH A NETWORK”,which is incorporated in its entirety but is not admitted to be priorart, I taught populating a Data Structure with identifying informationand device usage information such as channel tuning data to create afoundation upon which a comprehensive set of metrics can be produced. Inthat applications I taught loading the tuning data on a second-by-secondbasis into buckets in a data structure and populating the buckets with achannel call sign to indicate viewing of the channel during that second;I then used this as a basis for creating analytics.

In this application I populate a Video Viewing Analysis Data Structurewith information which identifies a video program being viewed, a videoprogram airing being viewed, and fields to identify the demographic,geographic, and device information related to the viewer and the viewingdevice he is using. In my previous Application, in one embodiment Itaught populating the buckets with a 1 to indicate viewing of thechannel during that second. In another previous application I taughtpopulating the buckets with a channel call sign to indicate viewing ofthe channel during that second. In this application, in one embodiment,I teach populating the bucket with various Activity Fields including (a)an identifier to indicate the activity of the user during that secondwith activity being things such as Play, Skip, Forward (at variousspeeds), Reverse (at various speeds), etc., (b) volume level, (c)foreground/background indicator, (d) percent content visible, (e)picture in picture indicator, (f) a percentage of screen this video, and(g) a viewer interaction score which assigns a value to the viewingactivity. The viewer interaction score reflects the level of userengagement with the video such that normal viewing earns a high scorewhile fast forward viewing or reverse viewing earns a reduced score.Additionally, other factors such as muted viewing, delayed viewing,occluded viewing, and other factors all reduce the score.

The reader will recognize that in each of these several embodiments Iteach loading values that identify second-by-second video programviewing activity to selected buckets in a viewing detail data structurebased on the beginning and ending time of the user interaction, thusidentifying second-by-second video program viewing activity showingwhether or not the video asset viewing device was viewing the videocontent during each second of a period of interest and measuring thelevel of user involvement during each second.

As noted, in this embodiment I introduce the concepts of calculatingviewing activity during trick plays to gain additional insight intoviewer behavior during playback of DVR and VOD assets and also duringcertain live viewing that supports trick plays.

By combining the teaching of my co-pending patent applications with theteachings of this application I am able to produce detailed viewingmetrics based on a one-second level of granularity for Linear, includingtime-shifted linear viewing, DVR and VOD viewing.

After populating the Video Viewing Analysis Data Structure, I can thenuse that data to calculate Linear, DVR, and VOD activity at threelevels: (a) the Video Program, (b) the Video Program Airing, and (c) theVideo Program Airing Segment. For each of these three levels, Icalculate viewing activity at additional levels of detail.

For the Video Program, I calculate viewing activity at the level ofDemographic identifier, Geographic identifier, and Viewing DeviceCharacteristic. Within the various Demo-Geo-Device combinations, Icalculate second-by-second viewing activity for each second of the VideoProgram.

For the Video Program Airing, I calculate viewing activity for multipleairings of the Video Program. This is done at the level of Demographicidentifier, Geographic identifier, and Viewing Device Characteristicwithin the Video Program Airing. Within the various Demo-Geo-Devicecombinations for the Program Airing, I calculate second-by-secondviewing activity for each second of the Video Program.

For the Video Program Airing Segment, I calculate viewing activity foreach of the various Segments that may be defined within the VideoProgram. Because each of the multiple airings of the Video Program willhave different viewings of the various Segments, I calculate viewing ofeach Segment within the context of the Video Program Airing. This isdone at the level of Demographic identifier, Geographic identifier, andViewing Device Characteristic within the Video Program Airing Segment.Within the various Demo-Geo-Device combinations for the Program AiringSegment, I calculate second-by-second viewing activity for each secondof the Video Program.

These various level of aggregation can be illustrated as follows: VideoProgram

-   -   Level 1—Video Program        -   Level 2—Demo-Geo-Device            -   Level 3—Second-by-second activity

Video Program Airing

-   -   Level 1—Video Program        -   Level 2—Video Program Airing            -   Level 3—Demo-Geo-Device                -   Level 4—Second-by-second activity

Video Program Airing Segment

-   -   Level 1—Video Program        -   Level 2—Video Program Airing            -   Level 3—Video Program Airing Segment                -   Level 4—Demo-Geo-Device                -    Level 5—Second-by-second activity

Once the data is captured at these three levels: (a) the Video Program,(b) the Video Program Airing, and (c) the Video Program Airing Segment,the system can run additional calculations to produce a verycomprehensive set of metrics on video asset viewing for linear, DVR, andVOD activity. The metrics can then be output as (i) data files that canbe read by a computer program, (ii) data base tables, (iii) electronicmessages, or (iv) a spreadsheet.

A person skilled in the art will readily see the benefits of loading theresulting metrics to a relational data base where additional queries andanalytics can be run using standard SQL. Additionally, the resultingfiles may be loaded to other statistical analysis tools or data basestructures. As a nonlimiting example, metrics calculated by theMeasurement Engine 200 can be loaded to a data base in support of longerterm analysis.

The Measurement Engine 200 presented in this embodiment provides theability to produce metrics with a level of detail not possiblepreviously. These metrics are described in detail in FIG. 17 (VideoProgram Viewing Activity Data Structure), FIG. 19 (Video Program AiringViewing Activity Data Structure), and FIG. 21 (Video Program AiringSegment Viewing Activity Data Structure). The metrics shown in theseFigures all provide information useful for understanding viewerbehavior; understanding how viewers interact with video programming ontraditional television and internet protocol television and other videoviewing devices; and understanding ad and program viewing habits. Suchmetrics will provide valuable information for advertisers, serviceproviders (cable television companies, satellite television companies,and/or internet protocol television providers), advertising agencies,and other interested parties. The Measurement Engine 200 then createsvarious files containing the calculated metrics in a format suitable forloading to a database.

These and other advantages of one or more aspects will become apparentfrom a consideration of the ensuing description and accompanyingdrawings.

Data Encryption

To protect the privacy of the viewer and/or to comply with various lawsand/or regulations, service providers (cable television companies,satellite television companies, and/or internet protocol televisionproviders) may anonymize and/or encrypt and/or de-identify any data thatcould identify a specific customer or viewer.

Within the various embodiments presented herein, applying consistentencryption algorithms to the video asset viewing device identifiers(Set-top box id's) in the Media Measurement database and the downstreamfiles allows the Measurement Engine 200 to produce the metricsidentified herein while protecting viewer privacy.

Definitions

The following are definitions that will aid in understanding one or moreof the embodiments presented herein:

Adjustment factors are those things which are used to adjust orcalculate or influence the viewer interaction score which identifies thevalue of the viewing activity. The following are nonlimiting examples ofadjustment factors: Volume level/Muting, Percent Content Visible,Foreground/Background viewing, Playback mode and Trick plays whileviewing, and delay in viewing DVR recorded programs, picture in picture,and percentage of screen this video.

Buckets means individual cells in a Data Structure. Nonlimiting examplesinclude:

(i) addressable fields in a table in a COBOL program,

(ii) addressable fields in an array or similar structure in a ‘C’program or a C++ program,

(iii) cells in a spreadsheet.

COBOL is the acronym of a business oriented computing language.

Computer readable format means any data format that can be read by acomputer program or a human being as necessary. Nonlimiting examplesinclude:

(i) formatted text files,

(ii) pipe delimited text files,

(iii) data base tables,

(iv) Extensible Markup Language (XML) messages

(v) a printed report.

Computer system accessed through a network means any computer system,any individual piece of computer equipment or electronic gear, or anycombination of computer equipment or electronic gear which enables orfacilitates the viewer interaction with the video asset viewing device.Nonlimiting examples include:

(i) cable television system,

(ii) cable television switched digital video system,

(iii) cellular phone network,

(iv) satellite television system,

(v) web server,

(vi) any individual piece of computer equipment or electronic gear,

(vii) any combination of computer equipment or electronic gear.

Data analysis computer system means a combination of one or morecomputers on which a Data Analysis Program or Programs can be executed.

Data analysis computer of known type means any commonly availablecomputer system running a commonly known operating system. Nonlimitingexamples include:

(i) a standard personal computer running WINDOWS® XP operating systemfrom MICROSOFT® Corporation,

(ii) a computer running the UNIX operating system,

(iii) a computer running the Linux operating system,

(iv) a computer in a cloud computing environment,

(v) a set-top box with its operating system,

(vi) A mainframe computer with its operating system,

(vii) a standard personal computer running WINDOWS 7 Professionaloperating system from MICROSOFT® Corporation.

Data analysis program means a computer program or programs that are ableto execute on a Data analysis computer of known type.

Data base table means any relational data base table structure orcomparable data base object.

Data structure means a place in a computer program or computer systemwhere data can be stored in tabular form with identifying fields andbuckets associated with those identifying fields in such a manner thatformula and algorithms can be run against the data to produce meaningfulmetrics. Nonlimiting examples include:

(i) table in a COBOL program,

(ii) array or similar structure in a ‘C’ program or a C++ program,

(iii) spreadsheet;

such structures may be stored in the memory of the computer, but theycould also be stored on electronic disk or other computer hardware.

Demographic information means any data item that can describe acharacteristic of a viewer or a subscriber or a household associatedwith a viewer who is operating the video asset viewing device.Nonlimiting examples include income, ethnicity, gender, age, maritalstatus, location, geographic area, postal code, census data, occupation,social grouping, family status, any proprietary demographic grouping,segmentation, credit score, dwelling type, homeownership status,property ownership status, rental status, vehicle ownership, tax rolls,credit card usage, religious affiliation, sports interest, politicalparty affiliation, cable television subscriber type, cable televisionsubscriber package level, and cell phone service level.

Derive, as used in ‘Derive Viewing Activity Information’ means anymethod or process of taking the source data and making it ready topopulate a destination field or fields. This may include a direct moveof the data from the source to the destination or it may include variouscalculations, substitutions, manipulations, or derivations performed onthe source data to make it ready to populate the destination fields orfields.

Device Characteristic means any feature or capability or aspect ordescriptive qualifier or identifier of a video viewing device.Nonlimiting examples include that this may identify the type of devicesuch as a set-top box, a tablet, a smart phone; a capability of thedevice such as the ability to record video or to support multipleviewing windows, or a manufacturer identifier.

Device Type is a subset of Device Characteristic where device type may,as a nonlimiting example, identify the type of device such as a set-topbox, a tablet, a smart phone.

Digital Video Recorder means a device that records video content from anetwork for later playback. This includes but is not limited to set-topbox DVR, network DVR, and cloud DVR.

DVR—see Digital Video Recorder.

Electronic message means any computer readable output that can be usedas input to another computer or read by a human. Nonlimiting examplesinclude:

(i) data output in Extensible Markup Language format,

(ii) data output in Hypertext Markup Language format, etc.

Geographic information means any service area or any network hierarchydesignation or marketing area or other designated area used by a cabletelevision company or a satellite television company or IP Televisiondelivery company or video asset delivery system. The boundary ordescription of a geographic area is defined based on the needs of theservice provider. Nonlimiting examples include a Market in a cablecompany network, a Headend in a cable company network, a Hub in a cablecompany network, a census tract, a cell tower identifier, a service areafor satellite TV, advertising zone, a zip code, or some other geographicidentifier. The geographic information may then be used to identify thelocation of a video asset viewing device or geographic information aboutthe about the house associated with the device or the location of thedevice at the time of the viewer interaction in the event that theviewer interaction occurs in a location different than the location ofthe house associated with the device.

Individual part of video content means any portion of video content thatmay be of interest in relation to measuring viewer interaction with thevideo content. Nonlimiting examples include:

(i) seconds of content,

(ii) minutes of content,

(iii) quarter hours of content,

(iv) hours of content,

(v) four hour blocks of content,

(vi) user defined segments of content,

(vii) a part of a second,

(viii) a group of seconds,

(ix) any other useful unit of time for measurement.

Interacting with video content means any interaction between the viewerand the video content including but not limited to viewing content,recording content, playing back recorded content including use of trickmodes. Recorded content can be DVR recording or VOD content.

Network means any computer network. Nonlimiting examples include:

(i) a cable television network,

(ii) a cellular telephony network,

(iii) hybrid fiber coax system,

(iv) a satellite television network,

(v) a wi-fi network,

(vi) any means that supports communication among video asset viewingdevices or electronic devices or computers or computer systems.

Outputting the contents means creating a delimited file, updating adatabase table, inserting to a database table, writing an XML message,or any activity that allows the calculated values to be used bydownstream processes.

Pipe delimited text files means data files where the fields areseparated by the “|” character.

Period of interest means a period of time with a defined starting pointand a defined ending point.

Populated based on the value of means using the value of a source fieldto set the value of a destination field where the source may be directlyloaded to the destination, or the source may be substituted with a codevalue which is then loaded to the destination, or the source may bemanipulated in some way to create the value which is loaded to thedestination.

Set-top box means a video asset viewing device that receives externalsignals and decodes those signals into content that can be viewed on atelevision screen or similar display device. The signals may come from acable television system, a satellite television system, a network, orany other suitable means. A set-top box may have one or more tuners. Theset-top box allows the user to interact with it to control what isdisplayed on the television screen. The set-top box is able to capturethe commands given by the user and then transmit those commands toanother computer system. For purposes of this application, stating thata set-top box tunes to a channel is equivalent to stating that a tunerin a set-top box has tuned to a channel. A set-top box may also playback previously recorded video content.

Spreadsheet means any commonly known electronic worksheet format.Nonlimiting examples include:

(i) MICROSOFT® EXCEL® files.

STB means Set-top box.

Take into account is a general term indicating that the value in thefield referred to is set using, or is calculated using, or is valued by,or is derived from, or is adjusted by, or is determined in some measureby another related field. The related field may be, but is not limitedto, video viewing session mode, video viewing session volume level,video viewing session percent content visible.

Trick Play Mode means using features of the video viewing device toexecute operations such as Play, Fast Forward at various speeds (1×, 2×,3×, 4×), Pause, Skip, Reverse at various speeds (1×, 2×, 3×, 4×), Slowplay, slow reverse, and similar activities.

Tuner means a tuner in a Set-top box.

Tuner index means an identifier of a tuner in a Set-top box.

Value identifying the viewing activity mode means any value thatidentifies the viewing activity type including but not limited tomnemonics such as PL, F1, R1 for Play, Forward 1× speed, Reverse 1×speed, or actual names such as Play, Forward 1×, Reverse 1×, or codesassigned to the activity such as 1 (for Play), 2 (for Reverse 1×), etc.All of these are nonlimiting examples.

Video asset means any programming content that may be viewed and/orheard. A Video Program may contain multiple Video Assets. Nonlimitingexamples of Video Asset include:

(i) advertisements or commercials,

(ii) movies,

(iii) sports programs,

(iv) news casts,

(v) music.

Video asset viewing device means any electronic device that may be usedeither directly or indirectly by a human being to interact with videocontent where the video content is provided by a cable television systemor a satellite television system or a computer system accessed through anetwork. Nonlimiting examples include: Gaming station, web browser, MP3Player, Internet Protocol phone, Internet Protocol television, mobiledevice, mobile smart phone, set-top box, satellite television receiver,set-top box in a cable television network, set-top box in a satellitetelevision system, cell phone, personal communication device, personalvideo recorder, personal video player, two-way interactive serviceplatforms, personal computer, tablet device.

Viewer means the human being causing a Viewer interaction; the user of aSet-top box or a Video asset viewing device.

Viewer interactions means any identifiable activity that a Video assetviewing device operator may do in regard to a Video asset viewing deviceand where such activity can be captured by the video asset viewingdevice or by the computer system, accessed through the network, thatsupports the device. Nonlimiting examples include:

(i) power on/power off, open web page, close web page,

(ii) channel up/channel down/channel selection, play video content onweb browser,

(iii) volume up/volume down/mute/unmute,

(iv) any trick play such as fast forward, rewind, pause

(v) recording video content,

(vi) playing back recorded video content,

(vii) invoking a menu, choosing a menu option,

(viii) any response to a screen prompt.

Viewers interacting with video content through a network means that thevideo content was delivered through a network. The content may be livecontent delivered through a network; or live content that was recordedon a local device at the time it was delivered through a network andthen played back later with or without the network access; or it may beDVR content in the cloud; or it may be Video on Demand content deliveredthrough a network.

Viewing activity information means information derived from any of thefollowing: Linear viewing including time-shifted linear viewing, DigitalVideo Recorder recording and playback/viewing, Video on Demand viewing.

Viewing activity type means the general category of viewing activityincluding but not limited to Linear viewing including time-shiftedlinear viewing, Digital Video Recorder recording and playback/viewing,Video on Demand viewing.

Viewing metrics means any value calculated by a Data Analysis Program.

Window of time of interest for analysis means any period of time duringwhich it is desired to measure the viewer interaction with a video assetviewing device accessed through a network. Nonlimiting examples include:

(i) minutes in a day,

(ii) commercial periods during a television program,

(iii) quarter hours of a day,

(iv) hours of a day,

(v) four hour blocks in a day,

(vi) days,

(vii) any period of time useful for analysis,

(viii) any period of time that can be defined by a starting date andtime and an ending date and time

Etc.

Viewer interaction score means a numeric value (score) or a rating or acharacter code (A, B, C, etc.) which is assigned to the viewing activitywhich identifies the value of the viewing activity. The viewerinteraction score is set according to various algorithmic rules whichtake into account various Adjustment factors.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, closely related figures have the same number butdifferent alphabetic suffixes.

FIG. 1 provides an overview of an exemplary process for collectingviewer interaction data derived from a plurality of viewers interactingwith video content that was delivered on a plurality of video assetviewing devices delivering content through a network and then loadingthat data to a Media Measurement Data Base.

FIG. 2 illustrates an exemplary data structure for the Video ViewingAnalysis Data Structure which Is used to record the second-by-secondviewing activity of a video program airing based on a Linear ViewingSession or a DVR Playback Session or a VOD viewing session.

FIG. 3 is a flowchart illustrating an overview of an exemplary processfor receiving (a) viewing activity stored in a Media MeasurementDatabase, and (b) data in various control files which controlprocessing, and then using a computer to analyze these data sources toproduce video viewing metrics, according to one embodiment.

FIG. 4 illustrates an exemplary flowchart for loading data from aPlayback Mode File 110 to a Playback Tally Rate Data Structure(reference FIG. 5-B) array in the memory of a computer in preparationfor analyzing video asset viewing activity, according to one embodiment.

FIG. 5 relates to Playback Mode. FIG. 5-A illustrates an exemplaryrecord layout for a Playback Mode File 110 record formatted for use asinput to the Measurement Engine 200, according to one embodiment. FIG.5-B illustrates an exemplary data structure for storing Playback Modedata in the memory of a computer for use by the Measurement Engine 200,according to one embodiment.

FIG. 6 illustrates an exemplary flowchart for loading data from aPlayback Delay Penalty Factor File 120 to a Playback Delay Penalty DataStructure array in the memory of a computer in preparation for analyzingvideo asset viewing activity, according to one embodiment.

FIG. 7 relates to Playback Delay Penalty. FIG. 7-A illustrates anexemplary record layout for a Playback Delay Penalty File 120 recordformatted for use as input to the Measurement Engine 200, according toone embodiment. This relates to part 120. FIG. 7-B illustrates anexemplary data structure for storing Playback Delay Penalty data in thememory of a computer for use by the Measurement Engine 200, according toone embodiment. FIG. 7-C illustrates sample data, according to oneembodiment.

FIG. 8 illustrates an exemplary flowchart for loading data from aHistogram Definition File 130 to a Histogram Definition Data Structurearray in the memory of a computer in preparation for analyzing videoasset viewing activity, according to one embodiment.

FIG. 9 relates to Histogram Definition. FIG. 9-A illustrates anexemplary record layout for a Histogram Definition File 130 recordformatted for use as input to the Measurement Engine 200, according toone embodiment. This relates to part 130. FIG. 9-B illustrates anexemplary data structure for storing Histogram Definition data in thememory of a computer for use by the Measurement Engine 200, according toone embodiment.

FIG. 10 illustrates an exemplary flowchart for loading data from a VideoProgram Airing File 150 to a Program Airing Data Structure array in thememory of a computer in preparation for analyzing video asset viewingactivity, according to one embodiment.

FIG. 11 illustrates an exemplary record layout for a Video ProgramAiring File 150 formatted for use as input to the Measurement Engine 200with FIG. 11 illustrating the file format, according to one embodiment.

FIG. 12 illustrates an exemplary flowchart for loading data from a VideoProgram Segment File 160 to a Program Segment Data Structure in thememory of a computer in preparation for analyzing video asset viewingactivity, according to one embodiment.

FIG. 13 illustrates an exemplary record layout for a Video ProgramSegment File 160 formatted for use as input to the Measurement Engine200, according to one embodiment. FIG. 13 relates to Video ProgramSegments. FIG. 13-A illustrates an exemplary record layout for a VideoProgram Segment File 160 record formatted for use as input to theMeasurement Engine 200, according to one embodiment. This relates topart 160. FIG. 13-B illustrates an exemplary data structure for storingVideo Program Segment data in the memory of a computer for use by theMeasurement Engine 200, according to one embodiment.

FIG. 14 illustrates an exemplary overview of a process for loading datafrom a Video Viewing Event File 170 to a Playback Activity DataStructure array in the memory of a computer and then an overview of thesteps involved in processing that data to analyze video asset viewingactivity, according to one embodiment.

FIG. 15 relates to the Video Viewing Event File. FIG. 15-A illustratesan exemplary record layout for Linear Viewing Activity—Video ViewingEvent File 170 formatted for use as input to the Measurement Engine 200,according to one embodiment. FIG. 15-B illustrates an exemplary recordlayout for DVR and VOD Viewing Activity—Video Viewing Event File 170formatted for use as input to the Measurement Engine 200, according toone embodiment.

FIG. 16 illustrates an exemplary flowchart for Calculating Video ProgramViewing activity at a second-by-second level by manipulating data in thememory of a computer, according to one embodiment.

FIG. 17 illustrates an exemplary data structure used for CalculatingVideo Program Viewing Activity in the memory of a computer, according toone embodiment.

FIG. 18 illustrates an exemplary flowchart for Calculating Video ProgramAiring Viewing activity at a second-by-second level by manipulating datain the memory of a computer, according to one embodiment.

FIG. 19 illustrates an exemplary data structure used for CalculatingVideo Program Airing Viewing Activity in the memory of a computer,according to one embodiment.

FIG. 20 illustrates an exemplary flowchart for Calculating Video ProgramAiring Segment Viewing Activity at a second-by-second level bymanipulating data in the memory of a computer, according to oneembodiment.

FIG. 21 illustrates an exemplary data structure used for CalculatingVideo Program Airing Segment Viewing Activity in the memory of acomputer, according to one embodiment.

FIG. 22 illustrates an exemplary flowchart for Calculating SummaryViewing Statistics for Video Program Statistics, Video Program AiringStatistics, and Video Program Airing Segment Statistics, by manipulatingdata in the memory of a computer, according to one embodiment.

FIG. 23 illustrates an exemplary process for writing the ViewingStatistics file 210, according to one embodiment.

FIG. 24 illustrates an exemplary process for writing the ViewingHistogram file, 220 according to one embodiment.

FIG. 25 illustrates an exemplary process for writing the Viewing ProgramDemo-Geo-Device Viewing file 230, according to one embodiment.

FIG. 26 illustrates an exemplary process for writing the Video ProgramViewing Activity by Second file 240, according to one embodiment.

FIG. 27 illustrates an exemplary process for writing the Viewing ProgramAiring Demo-Geo-Device Viewing file 250, according to one embodiment.

FIG. 28 illustrates an exemplary process for writing the Viewing ProgramAiring Viewing Activity by Second file 260, according to one embodiment.

FIG. 29 illustrates an exemplary process for writing the Video ProgramAiring Segment file 270, according to one embodiment.

FIG. 30 illustrates an exemplary process for writing the Viewing ProgramAiring Segment Demo-Geo-Device Viewing file 280, according to oneembodiment.

FIG. 31 illustrates an exemplary process for writing the Video ProgramAiring Segment Viewing Activity by Second file 290, according to oneembodiment.

FIG. 32 illustrates summary information and an exemplary record layoutfor the Viewing Statistics file 210 which is produced by the MeasurementEngine 200 as a result of calculating video asset viewing activity.

FIG. 33 illustrates summary information and an exemplary record layoutfor the Viewing Histogram file 220 which is produced by the MeasurementEngine 200 as a result of calculating video asset viewing activity.

FIG. 34 illustrates summary information and an exemplary record layoutfor the Video Program Demographic Geographic Device Viewing file 230which is produced by the Measurement Engine 200 as a result ofcalculating video asset viewing activity.

FIG. 35 illustrates summary information and an exemplary record layoutfor the Video Program Viewing Activity by Second file 240 which isproduced by the Measurement Engine 200 as a result of calculating videoasset viewing activity by second.

FIG. 36 illustrates summary information and an exemplary record layoutfor the Video Program Airing Demographic Geographic Device Viewing file250 which is produced by the Measurement Engine 200 as a result ofcalculating video asset viewing activity.

FIG. 37 illustrates summary information and an exemplary record layoutfor the Viewing Program Airing Viewing Activity by Second file 260 whichis produced by the Measurement Engine 200 as a result of calculatingvideo asset viewing activity by second.

FIG. 38 illustrates summary information and an exemplary record layoutfor the Video Program Airing Segment file 270 which is produced by theMeasurement Engine 200 as a result of calculating video asset viewingactivity by second.

FIG. 39 illustrates summary information and an exemplary record layoutfor the Video Program Airing Segment Demographic Geographic Device file280 which is produced by the Measurement Engine 200 as a result ofcalculating video asset viewing activity by second.

FIG. 40 illustrates summary information and an exemplary record layoutfor the Video Program Airing Segment Viewing Activity by Second file 290which is produced by the Measurement Engine 200 as a result ofcalculating video asset segment viewing activity by second.

FIG. 41 illustrates an exemplary process for writing the data in theVideo Viewing Analysis Data Structure to the Video Viewing Analysis File205, according to one embodiment.

FIG. 42 illustrates an exemplary record layout for the Video ViewingAnalysis File 205 which is produced by the Measurement Engine 200.

DETAILED DESCRIPTION OF THE DRAWINGS

When reading the information below, it can be appreciated that these aremerely samples of table layouts, format and content, and many aspects ofthese tables may be varied or expanded within the scope of theembodiment. The table layouts, field formats and content, algorithms,and other aspects are what I presently contemplate for this embodiment,but other table layouts, field formats and content, algorithms, etc. canbe used. The algorithms are samples and various aspects of thealgorithms may be varied or expanded within the scope of the embodiment.

Note on Claims reference in drawings because of the large number of datafields and new concepts taught in this specification, and because adescription in the drawings may not use the exact same words or spellingas the corresponding concept in the claims, the reader will note that inlimited cases I have added text preceded by the words “Claims reference”to assist the reader in correlating information in the drawings ordetailed description of the drawings with the corresponding informationin the claims. These references are not meant in any way to restrict theClaims, but rather to clarify the relationship between the Claims andthe Specification.

For many of the metrics shown below, I have suggested what the metricindicates. This is not to limit the purpose of the metric to that oneusage, but simply to indicate one of potentially many valuable uses forthe metric.

Note that the specification and drawings use certain termsinterchangeably. The reader will note this most frequently with theterms set-top box and video asset viewing device. The reader willappreciate that a set-top box is merely a specific kind of video assetviewing device. A smart phone, a tablet device, a gaming console are allexamples of video asset viewing device. Thus any discussion herein thatrefers to a set-top box should be read to also include any kind of avideo asset viewing device.

In one embodiment the Measurement Engine 200 can be implemented onprocessors provided by the INTEL® Corporation under the trademark Core™i3-2120 using single or multiple processor configurations. The operatingsystem offered by MICROSOFT® Corporation under the trademark WINDOWS 7Professional can be used as the computer operating system. TheMeasurement Engine 200 can be implemented in a number of programminglanguages, including but not limited to, COBOL, C and C++.

I have implemented the Measurement Engine 200 and supporting code inFUJITSU® NetCOBOL® for WINDOWS® version 10.1 developed by Fujitsu® anddistributed by Alchemy Solutions Inc. This product is available athttp://www.alchemysolutions.com or http://www.netcobol.com. TheMeasurement Engine 200 and all of the supporting processes have beendeveloped and run on a DELL® Vostro 260 with INTEL® Core™ i3-2120 CPU3.30 GHz with 4.00 GB of RAM running MICROSOFT® WINDOWS 7 ProfessionalService Pack 1. The computer was purchased from Dell ComputerCorporation. The operating system is from Microsoft.

Although the embodiments described herein enable one of ordinary skillin the art to implement (i.e. build) the Measurement Engine 200 andsupporting software, it in no way restricts the method ofimplementation, the Measurement Engine 200 and supporting software beingcapable of being implemented on a variety of hardware/software platformsusing a variety of development languages, databases, communicationprotocols and frameworks as will be evident to those of ordinary skillin the art.

Note on Media Measurement Data Model

Cable Television Laboratories, Inc. has published a confidential“Audience Data Measurement Specification” as “OpenCable™ Specifications,Audience Measurement, Audience Measurement Data Specification” havingDocument Control Number “OC-SP-AMD-D01-120711” copyright © CableTelevision Laboratories, Inc. 2012 which contains a Media MeasurementData Model database design which can be used as a source of data to theMeasurement Engine 200 which I teach how to build in this Application.The teaching in my present application can be implemented in conjunctionwith that Media Measurement Data Model or with any number of data modelsas long as the required input data is provided as described herein.

Additionally, my Measurement Engine 200 creates files which may be usedto load additional tables in a Media Measurement Data Model such as theone published by Cable Television Laboratories, Inc. These files aredescribed in FIGS. 32 to 40.

Note: Numbering in the Drawings—The numbers in the drawings are usually,but not always, in sequential order.

FIG. 1 provides an overview of an exemplary process for collectingviewer interaction data derived from a plurality of viewers interactingwith video content that was delivered on a plurality of video assetviewing devices delivering content through a network and then loadingthat data to a Media Measurement Data Base. This figure illustratesseveral viewers interacting with video asset viewing devices to viewcontent which was delivered to those devices across a network and thento collect viewing activity from those devices.

In this nonlimiting example, the purpose is not to describe in detailthe operations of video content delivery network or a data collectionprocess, but simply to show how the data that is collected from thatsystem can be made available to my Measurement Engine 200.

It begins with Viewer Viewing Linear Content 9200 who is interactingwith a set-top box 9210 and television 9220 as he views linear content.The set-top box 9210 interacts with a Video Content Delivery System 9250which delivers the content across a Network 9230.

It continues with Viewer Viewing DVR Content 9202 who is interactingwith a set-top box 9210 and television 9220 as he interacts with DVRcontent recording content and playing back recorded content usingvarious modes including trick plays. The set-top box 9210 interacts witha Video Content Delivery System 9250 which delivers the content across aNetwork 9230.

It continues with Viewer Viewing VOD Content 9203 who is interactingwith a set-top box 9210 and television 9220 as he interacts with VODcontent playing the content using various modes including trick plays.The set-top box 9210 interacts with a Video Content Delivery System 9250which delivers the content across a Network 9230.

It continues with Viewer viewing video content using tablet, smartphone, IP TV, or other video video viewing device 9204 who isinteracting with a variety of video viewing devices, including but notlimited to tablet, smart phone, IP TV, PC, etc. The video viewing deviceinteracts with a Video Content Delivery System 9250 which delivers thecontent across a Network 9230.

Video Content Delivery System 9250 then interacts with a ViewerInteraction Data, Data Collection System 9260 which collects all mannerof viewer interaction data including Linear viewing includingtime-shifted linear viewing, Digital Video Recorder recording andplayback/viewing, and Video on Demand viewing. The Viewer InteractionData, Data Collection System 9260 then processes the data as needed toload it to a Media Measurement Data Base 100. The data in the MediaMeasurement Data Base 100 can then be used as input to my MeasurementEngine 200 as described in FIG. 3.

FIG. 2 provides summary information about and illustrates an exemplarydata structure which is used by the Measurement Engine 200 for storingand processing viewer interaction data so that the data can be used toproduce viewing statistics regarding Video Program Viewing, VideoProgram Airing Viewing, Video Program Airing Segment Viewing, andViewing grouped into Histogram buckets, according to one embodiment.

The viewer interaction data can be Linear viewing activity includingtime-shifted linear viewing, DVR viewing activity (recording andplayback), or VOD viewing activity. The value assigned toPAA-RECORD-PLAYBACK-SESSION-ID 4030 will vary depending upon whether theviewing activity is Linear, DVR, or VOD; this value is set from data inthe Video Viewing Event File 170 (FIG. 15). This data structure allowsthe Measurement Engine 200 to combine any number of viewing actions(play, fast forward, reverse, mute, switch screens, etc.) that may occurwithin a Linear Viewing Session or a DVR Playback Session or a VODviewing session to produce second-by-second viewing activity for all theactions during the session. That second-by-second activity is then in aformat which enables calculation of Video Program Viewing, Video ProgramAiring Viewing, Video Program Airing Segment Viewing, and Viewinggrouped into Histogram buckets. This structure also allows theMeasurement Engine 200 to identify the viewing by Demographic,Geographic, and Device Characteristic combinations so that downstreamaggregation can be done for each of the various combinations of thosefields.

Claims Reference: In the claims this is referred to as the Video ViewingAnalysis Data Structure.

Claims Reference: In the Video Viewing Analysis Data Structure (FIG. 2),Identifying Fields are 4010, 4013, 4020, 4025, 4030, 4040, 4045, 4050.

Claims Reference: By putting this data structure (FIG. 2) into theMeasurement Engine 200 it provides computer readable access to the VideoViewing Analysis Data Structure containing viewing activity informationwhich was loaded to the Video Viewing Analysis Data Structure inpreparation for analyzing a plurality of viewer interactions resultingfrom the viewers interacting with the video content.

Alternative Embodiment: This same Video Viewing Analysis Data Structurecould be implemented in a subprogram, a database table, a databasestructure, or other similar method and still accomplish a similarresult.

FIG. 3 is a flowchart illustrating an overview of an exemplary processfor providing (a) Video Program and Video Program Airing data from aMedia Measurement database, (b) Video Program Segment data from a MediaMeasurement database, (c) Video Viewing Event data from a MediaMeasurement database, (d) Playback Mode data, (e) Playback Delay PenaltyFactor data, (f) and Histogram Definition data to a Measurement Engine200 and then using these data sources to produce viewing metrics,according to one embodiment.

The populating of the Media Measurement Database 100 is beyond the scopeof this application and so only brief remarks will be made in referenceto that. There are video program scheduling systems that are commonlyused in the industry that can provide the Video Program data, the VideoProgram Airing data, and the Video Program Airing Segment data.Additionally there are systems that are commonly used for collectingchannel tuning or video viewing event data including switched digitalvideo systems and set top box applications, internet protocol videoviewing applications, and other video viewing applications. Such systemsare common in the industry. Playback Mode data, Playback Delay PenaltyFactor data, and Histogram definition data are reference valuesspecified by the analyst. All of these sources together provide theneeded inputs to the Measurement Engine 200. This data can be deliveredto the Measurement Engine 200 in any computer readable format including,but not limited to, database tables, flat files, and XML messages.

Proceeding with the review of FIG. 3, a Playback Mode File 110(reference FIG. 5) is provided as input to the Measurement Engine 200.The Playback Mode File 110 records the various play or playback modeswhich a viewer may use to control video viewing. This includes modes forlinear viewing and DVR playback and VOD playback. The file allows theAnalyst to specify that amount of viewing credit or points that can beearned for each part (second) of video content when a video is viewed inany of these modes. For example, mode Play may earn 1 point; mode Skipmay earn 0 points; mode F3 may earn 0.2 points. The point scoring iscontrolled by the Analyst when he specifies the values in this file.These values will then be applied to the video viewing activity as partof the scoring algorithm.

Proceeding with the review of FIG. 3, a Playback Delay Penalty FactorFile 120 (reference FIG. 7) is provided as input to the MeasurementEngine 200. The Playback Delay Penalty Factor File 120 records theinformation about what amount of penalty or reduction to apply to theviewing based on delay in viewing or playback. This file allows theAnalyst to control the points earned from video viewing with currentviewing earning the most points while viewing that is significantlydelayed earns fewer points. This functionality recognizes thatadvertisers get the most value for the ads when viewing is live or nearto live.

The Playback Delay Penalty Factor File 120 can be used with linearviewing and DVR playback and VOD playback.

Proceeding with the review of FIG. 3, a Histogram Definition File 130(reference FIG. 9) is provided as input to the Measurement Engine 200.The Histogram Definition File 130 records the information which allowsthe analyst to group viewing into buckets based on ranges defined in thehistogram file where the buckets indicate the duration of the viewingsession. This provides the Analyst with insight into whether a videoprogram is getting many short viewing sessions or fewer longer viewingsessions.

Proceeding with the review of FIG. 3, a Video Program Airing File 150(reference FIG. 11) is provided as input to the Measurement Engine 200.The Video Program Airing File 150 records the information about thevideo program and the various airings of the video program for which theMeasurement Engine 200 is tracking viewing activity. If a video programhas been aired multiple times, this allows the analyst to specify thoseairings for which viewing activity will be measured; this may be asubset of the all the airings that occurred.

Proceeding with the review of FIG. 3, a Video Program Segment File 160(reference FIG. 13) is provided as input to the Measurement Engine 200.The Video Program Segment File 160 records the information about thevarious segments of the video program for which the Measurement Engine200 is tracking viewing activity. The Analyst may specify varioussegments or program parts for which viewing is to be tracked. A Segmentmay be when an advertisement is airing or it may be part of the programcontent. By defining Segments the Analyst is able to specify particularportions of the video program for which viewing activity will bemeasured; this may be a subset of the video content.

Proceeding with the review of FIG. 3, a Video Viewing Event File 170(reference FIG. 15) is provided as input to the Measurement Engine 200.The Video Viewing Event File 170 contains the Viewer Interaction Datathat will be input to the Measurement Engine 200 which will then analyzethe viewing activity represented by those viewer interactions. VideoViewing Event File 170 contains information identifying the VideoProgram that was viewed, the Video Program Airing information,Demographic, Geographic, and Device information, and event play orplayback information. All of this information is gathered from the MediaMeasurement Database 100 and provides the information about the set ofevents that the Analyst wants to measure.

Proceeding with the review of FIG. 3, Measurement Engine 200 (referenceFIG. 14 for an overview) takes the various inputs as defined herein andthen calculates viewing activity for the Video Program, for the VideoProgram Airing, for the Video Program Airing Segment, and for theHistogram and then writes the various output files as will be definedbelow and as shown in FIG. 3.

The Measurement Engine 200 as presently configured accepts flat files asinput and creates flat files as its output. Those skilled in the artwill readily recognize that the Measurement Engine 200 could just aseasily read database tables or XML messages or any other computerreadable format for its input. It could then produce XML messages orupdate database tables for its output or produce flat files as it doesin the present embodiment.

Proceeding with the review of FIG. 3, a Video Viewing Analysis File 205(reference FIG. 41) is created as output from the Measurement Engine200. The Video Viewing Analysis File 205 records the data from the VideoViewing Analysis Data Structure; this is the analyzed detail data whichwas used as input to the summarization process. This provides thepicture of the analyzed viewing activity data at a session level. Thisdata can be used for additional analysis.

Proceeding with the review of FIG. 3, a Viewing Statistics File 210(reference FIG. 32) is created as output from the Measurement Engine200. The Viewing Statistics File 210 records various statistics aboutthe overall video program viewing activity based on the viewing activityidentified in the Viewing Event File 170.

Proceeding with the review of FIG. 3, a Viewing Histogram File 220(reference FIG. 33) is created as output from the Measurement Engine200. The Viewing Histogram File 220 records various statistics about theoverall video program viewing activity grouped into the histogrambuckets that the user defined using the Histogram Definition file 130.

Proceeding with the review of FIG. 3, an Video Program DemographicGeographic Device Viewing File 230 (reference FIG. 34) is created asoutput from the Measurement Engine 200. The Video Program DemographicGeographic Device Viewing File 230 records various statistics about theVideo Program viewing activity broken down by various the Demographic,Geographic, and Device combinations defined in the Viewing Event File170.

Proceeding with the review of FIG. 3, an Video Program Viewing Activityby Second File 240 (reference FIG. 35) is created as output from theMeasurement Engine 200. The Video Program Viewing Activity by SecondFile 240 records the second-by-second viewing activity of this VideoProgram based on the viewing activity identified in the Viewing EventFile 170.

Proceeding with the review of FIG. 3, an Video Program AiringDemographic Geographic Device Viewing File 250 (reference FIG. 36) iscreated as output from the Measurement Engine 200.

The Video Program Airing Demographic Geographic Device Viewing File 250records summary information regarding viewership of this Video ProgramAiring aggregated to the level of Demographic—Geographic—Device groupingbased on the viewing activity identified in the Viewing Event File 170.This data is calculated at the video program airing level for each VideoProgram Airing defined in the Video Program Airing File 150 with theresult that the Analyst gets insight into viewing activity against eachairing of a video program based on the viewing activity identified inthe Viewing Event File 170.

Proceeding with the review of FIG. 3, an Video Program Airing ViewingActivity by Second File 260 (reference FIG. 37) is created as outputfrom the Measurement Engine 200. The Video Program Airing ViewingActivity by Second File 260 records the second-by-second viewingactivity of this Video Program Airing based on the viewing activityidentified in the Viewing Event File 170.

Proceeding with the review of FIG. 3, a Video Program Airing SegmentFile 270 (reference FIG. 38) is created as output from the MeasurementEngine 200. The Video Program Airing Segment File 270 records eachcombination of Video Program Airing along with the Segment details. Thisfile brings together the Video Program, the Video Program Airing, andthe Video Program Segment. In the downstream reporting database this canserve as the parent for the the summary information regarding theviewing activity at the Video Program Airing Segment level.

Proceeding with the review of FIG. 3, an Video Program Airing SegmentDemographic Geographic Device Viewing File 280 (reference FIG. 39) iscreated as output from the Measurement Engine 200. The Video ProgramAiring Segment Demographic Geographic Device Viewing File 280 recordssummary information regarding viewership of this Video Program AiringSegment aggregated to the level of Demographic—Geographic—Devicegrouping based on the viewing activity identified in the Viewing EventFile 170. This data is calculated at the video program airing and videoprogram segment level, so it provides insight into viewing activityagainst each airing of a video program segment. The Video ProgramAirings for which viewing will be calculated are defined in the VideoProgram Airing File 150. The Video Program Segments for which viewingwill be calculated are defined in the Video Program Airing Segment File160.

Proceeding with the review of FIG. 3, an Video Program Airing SegmentViewing Activity by Second 290 (reference FIG. 40) is created as outputfrom the Measurement Engine 200. The Video Video Program Airing SegmentViewing Activity by Second 290 records the second-by-second viewingactivity of this Video Program Airing Segment based on the viewingactivity identified in the Viewing Event File 170.

Each of the output files identified above, 205-290, may be loaded to adata base in support of further analytics. Those with ordinary skill inthe art will have no difficulty using common software development toolsto develop a process which loads files like the ones shown to a database or data warehouse in support of additional reporting and analytics.Alternatively, the Measurement Engine 200 could update data base tableshaving structures similar to those shown in output files 205-290.

To recap the output files that are created related to Video Programviewing, the Measurement Engine 200 has created files at three levels:(a) the Video Program, (b) the Video Program Airing, and (c) the VideoProgram Airing Segment. In each case, there is a summary file and asecond-by-second file. Note that each of these files provides breakoutsfor Demographic, Geographic, and Device attributes thus providingdetailed insight into the viewers who are consuming the video content.Additionally, it has created a file of the analyzed detail data whichwas used as input to the summarization process; this file can be used insupport of further analytics.

In addition, Measurement Engine 200 has created files for overallViewing Statistics, for Histogram, and the Video Program Airing Segmentfile used to provide a parent record in the database.

The end result is that the analyst has very detailed informationregarding viewing activity for each video asset. The analyst now has alevel of understanding of audience viewership never before possible forlinear, DVR, and VOD content.

FIG. 4 is a flowchart which illustrates an exemplary process for loadingthe Playback Mode File 110 into a Playback Tally Rate Data Structure(FIG. 5-B) in the memory of a computer that is running the MeasurementEngine 200, so that this data can be used by Measurement Engine 200 incalculating the amount of viewing credit or points that can be earnedfor each part (second) of video content when a video is viewed in any ofthese modes. For example, mode Play may earn 1 point; mode Skip may earn0 points; mode F3 may earn 0.2 points. The point scoring is controlledby the Analyst by specifying the values in this file. These values willthen be applied to the video viewing activity as part of the scoringalgorithm.

The process begins with Load Playback Tally Rate Data Structure 400. Theprocess then executes Read Playback Mode file 410 which reads filePlayback Mode File 110 as input. The process checks for End of File 420.If it is the end of file, the process is Done 440. If End of File 420does not detect an end of file condition, then the record that was readis loaded to the array using Load Playback Tally Rate Data Structure430.

The end result of this process is that the Measurement Engine 200 hasloaded the Playback Tally Rate data into an Data Structure in the memoryof the computer.

Additional detail on step Load Playback Tally Rate Data Structure 430follows:

The source code for this routine can be found in the accompanying sourcecode file as routines C110-LOAD-DVR-PB-TALLY-RATE andC112-LOAD-DVR-PB-TALLY-RATE which are included herein by reference.

FIG. 5 relates to Playback Mode.

FIG. 5-A illustrates an exemplary record layout for a Playback Mode File110 record formatted for use as input to the Measurement Engine 200,according to one embodiment. This relates to part 110.

FIG. 5-B illustrates an exemplary Data Structure for storing PlaybackMode data in the memory of a computer for use by the Measurement Engine200, according to one embodiment. In the Playback Mode File 110, thefield Playback Tally Rate 4220 which is loaded to 4270 tells the valueto assign for each playback mode. The analyst is able to control theviewing value assigned to each playback mode. Normal viewing is talliedat a rate of 1 per part (second). Suggested values for other viewingmodes are as shown.

In this embodiment, the playback mode is assigned a 1 to signify normalviewing and a reduced value for other viewing such as viewing duringtrick plays. Another embodiment may assign different values to achievethe same result.

FIG. 6 is a flowchart which illustrates an exemplary process for loadingthe Load Playback Delay Penalty Data Structure 450 into an array in thememory of a computer that is running the the Measurement Engine 200, sothat this data can be used by Measurement Engine 200 in calculating theamount of penalty or reduction to apply to the viewing based on delay inviewing or playback.

The Playback Delay Penalty Factor File 120 can be used with linearviewing and DVR playback and VOD playback. In this embodiment, forlinear viewing, there is no delay so the value is 1; for DVR viewingwhere the viewer is viewing a recording with ads that are not dynamic,the Analyst is able to specify reduced credit for delayed viewing;similarly with VOD, for ads that are not dynamic, the Analyst is able tospecify reduced credit for delayed viewing. Dynamic ads that areinserted at the time of viewing would have a factor of 1 indicating nodelay penalty.

The process begins with Load Playback Delay Penalty Data Structure 450.The process then executes Read Playback Delay Penalty Factor File 460which reads file Playback Delay Penalty Factor File 120 as input. Theprocess checks for End of File 470. If it is the end of file, theprocess is Done 480. If End of File 470 does not detect an end of filecondition, then the record that was read is loaded to the array usingLoad Delay Penalty Data Structure 490.

The end result of this process is that the Measurement Engine 200 hasloaded the Playback Delay Penalty data into a Data Structure in thememory of the computer running the engine.

Additional detail on step Load Delay Penalty Data Structure 490 follows:

The source code for this routine can be found in the accompanying sourcecode file as routines C120-LOAD-DVR-PB-DELAY-PENALTY andC122-DVR-PB-DELAY-PENALTY which are included herein by reference.

FIG. 7 relates to Playback Delay Penalty.

FIG. 7-A illustrates an exemplary record layout for a Playback DelayPenalty File 120 record formatted for use as input to the MeasurementEngine 200, according to one embodiment. This relates to part 120. Inthe program this file is named: 02-playback-delay-penalty-file.dat

FIG. 7-B illustrates an exemplary Data Structure for storing PlaybackDelay Penalty data in the memory of a computer for use by theMeasurement Engine 200, according to one embodiment.

FIG. 7-C illustrates sample data, according to one embodiment.

Playback Delay Penalty that tells the value by which to adjust theviewing score based on the delay in hours from recording to playback.Industry norms suggest that stale viewing should count less from anadvertising perspective. This table allows the analyst to control whatkind of delay factor should be applied in the case of stale viewing.

In this embodiment, the Playback Delay Penalty Factors are values lessthan 1 so that when they are used in the scoring algorithm, they reducethe viewing score, i.e.: multiplying by a value less then 1 produces asmaller value. In another embodiment, these could be negative valuesthat when added to the score reduce it.

FIG. 8 is a flowchart which illustrates an exemplary process for loadingthe Histogram Definition Data into an array in the memory of a computerthat is running the Measurement Engine 200, so that this data can beused by Measurement Engine 200 in grouping aggregate Video Programviewing by the Histogram Definitions defined in the file, according toone embodiment.

The process begins with Load Histogram Definition Data Structure 500.The process then executes Read Histogram Definition file 510 which readsfile Histogram Definition File 130 as input. The process checks for Endof File 520. If it is the end of file, the process is Done 540. If Endof File 520 does not detect an end of file condition, then the recordthat was read is loaded to the array using Load Histogram DefinitionData Structure 530.

The end result of this process is that the Measurement Engine 200 hasloaded the Histogram Definition data into a Data Structure in the memoryof the computer running the engine.

Additional detail on step Load Histogram Definition Data Structure 530follows:

The source code for this routine can be found in the accompanying sourcecode file as routines C130-LOAD-DVR-HISTOGRAM-DEF andC134-LOAD-DVR-HISTOGRAM-DEF which is included herein by reference.

FIG. 9 relates to Histogram Definition.

FIG. 9-A illustrates an exemplary record layout for a HistogramDefinition File 130 record formatted for use as input to the MeasurementEngine 200, according to one embodiment. This relates to part 130. Inthe program this file is named: 03-Histogram-Definition.dat

Claims Reference: FIG. 9-A describes Histogram Definitions containingviewing duration ranges.

FIG. 9-B illustrates an exemplary Data Structure for storing HistogramDefinition data in the memory of a computer for use by the MeasurementEngine 200, according to one embodiment.

Histogram Definition provides the beginning and ending number of secondsfor each of the histogram buckets along with the bucket name.

Claims Reference: FIG. 9-B describes Histogram Definitions containingviewing duration ranges.

FIG. 10 is a flowchart which illustrates an exemplary process forloading the video program airings that are to be analyzed into an DataStructure in the memory of a computer that is running the MeasurementEngine 200, so that this data can be used by Measurement Engine 200 asit tracks viewing activity against these video program airings. Theprocess begins with Load Video Program Airing Data Structure 550. Theprocess then executes Read Video Program Airing File 560 which readsfile Video Program Airing File 150 as input. The process checks for Endof File 570. If it is the end of file, the process is Done 590. If Endof File 570 does not detect an end of file condition, then the recordthat was read is loaded to the Data Structure using Load Video ProgramAiring Data Structure 580.

The end result of this process is that the Measurement Engine 200 hasloaded the Video Program Airing data into a Data Structure in the memoryof the computer running the engine. Note that the Video Program Airingdata from the input file is loaded directly to the Video Program AiringViewing Activity (ref FIG. 19) and to the Video Program Airing SegmentViewing Activity (ref FIG. 21).

Additional detail on step Load Video Program Airing Data Structure 580follows: The source code for this routine can be found in theaccompanying source code file as routines C130-LOAD-VIDEO-PROGRAM-AIRINGand C132-VIDEO-PROGRAM-AIRING which is included herein by reference.

FIG. 11 illustrates an exemplary record layout illustrating the fileformat for a Video Program Airing File 150 formatted for use as input tothe Measurement Engine 200, according to one embodiment. Note that theVideo Program Id to which this Video Program Airing data applies isincluded in the file as IN-VPA-VIDEO-PROGRAM-ID 4520.

FIG. 12 is a flowchart which illustrates an exemplary process forloading the video program segments that are to be analyzed into a DataStructure in the memory of a computer that is running the MeasurementEngine 200, so that this data can be used by Measurement Engine 200 asit tracks viewing activity against these video program segment airings.The process begins with Load Video Program Segment Data Structure 600.The process then executes Read Video Program Segment File 610 whichreads file Video Program Segment File 160 as input. The process checksfor End of File 620. If it is the end of file, the process is Done 640.If End of File 620 does not detect an end of file condition, then therecord that was read is loaded to the array using Load Video ProgramSegment Data Structure 630.

The end result of this process is that the Measurement Engine 200 hasloaded the Video Program Segment data into a Data Structure in thememory of the computer running the engine.

Additional detail on step Load Video Program Segment Data Structure 630follows: The source code for this routine can be found in theaccompanying source code file as routines C140-LOAD-VIDEO-PGM-AIRING-SEGand C142-VIDEO-PROGRAM-SEG-ARRAY which is included herein by reference.

FIG. 13 relates to Video Program Segments.

FIG. 13-A illustrates an exemplary record layout for a Video ProgramSegment File 160 formatted for use as input to the Measurement Engine200, according to one embodiment. The Video Program Segment File 160contains all of the video segments for which the Measurement Engine 200will analyze viewing activity. These records are read and loaded to a

Video Program Segment Data Structure (ref FIG. 13-B). Then the group ofrecords is copied forward to each individual airing of the program forwhich the Measurement Engine 200 is analyzing viewing activity so thateach airing has all of the Segments. This copy process is done as partof the initialization process.

This data is loaded to the Video Program Airing Segment Viewing ActivityData Structure FIG. 21 at the start of processing. Reference routinesC140-LOAD-VIDEO-PGM-AIRING-SEG, C142-VIDEO-PROGRAM-SEG-ARRAY,C146-COPY-SEG-DATA-TO-PGM-AIR.

A segment can be any part of the program up to 60 seconds. A nonlimitingexample to show the concept is:

-   -   Segment Beg Sec End Sec    -   00000 to 00059    -   00060 to 00119    -   09000 to 09059    -   10000 to 10029

The Segment Begin Time Second in Program is based on starting at 0 sincethat would equate to the actual start of the program.

In the program the Video Program Segment File 160 is named:05-video-program-airing-segment.dat

FIG. 13-B illustrates an exemplary data structure for storing VideoProgram Segment Data Structure in the memory of a computer for use bythe Measurement Engine 200, according to one embodiment.

FIG. 14 is a flowchart which illustrates an exemplary process forloading viewer interaction data to Video Viewing Analysis Data Structuredata structure (Reference FIG. 2) in the memory of a computer that isrunning the the Measurement Engine 200 and then running variousanalytics against that data to calculate Video Program Viewing, VideoProgram Airing Viewing, Video Program Airing Segment Viewing, on both anaggregate level and a second-by-second level.

The process begins with Processing Video Event File Overview 700. Theprocess then executes Read Video Viewing Event File 710 which reads fileVideo Viewing Event File 170 as input. The process checks for End ofFile 715. If it is the end of file, the process is proceeds to Go toProcess Final Set of records 720 where the data for the last set ofrecords is processed prior to the final calculations. If End of File 715does not detect an end of file condition, then the Measurement Engine200 compares the key fields (Video Program Airing Id,House-Device-Viewer, Demographic-Geographic-Device id, Viewing Sessionor Playback Id) in the input record to the saved key fields. If the keyis the same and thus Same Key 725 is true, the program proceeds to LoadViewing Activity to Video Viewing Analysis Data Structure 730 where theviewing activity represented in the event record is loaded to the datastructure.

If the key is not the same, then the Measurement Engine 200 proceeds towrite the Video Viewing Analysis Data File 783, Calculate HistogramViewing 785, then aggregate the second-by-second viewing activity forthe Video Program Viewing, the Video Program Airing Viewing, and theVideo Program Segment Viewing using the viewing activity informationthat was loaded to the Video Viewing Analysis Data Structure (Ref FIG.2). After all the calculations are done, the new values are moved to thesave fields.

The first step is Write Video Viewing Analysis Data File 783 whichwrites the data in the Video Viewing Analysis Data Structure (FIG. 2) tofile Video Viewing Analysis File 205. This is further explained in FIG.41.

The next step is to do Calculate Histogram Viewing 785 where theMeasurement Engine 200 calculates various metrics based on a histogramdefinition. The measurement engine compares the playback duration to theboundaries of the histogram buckets that were loaded as described inFIG. 8. When the correct range is found, the session duration is addedto the Histogram bucket total viewing seconds and the session count forthat bucket is incremented by 1. The source code for this routine can befound in the accompanying source code file as routinesD140-TABULATE-HISTOGRAM which is included herein by reference.

Video Viewing Histogram Data Structure (FIG. 9-B) Identifying Fields arepopulated as follows: video program identifier 4462 fromPAA-VIDEO-PROGRAM-ID 4010 (reference FIG. 2) viewing activity type 4463from PAA-VIEWING_ACTIVITY_TYPE 4013 (reference FIG. 2) demographic code4464 from PAA-HOUSE-DEMOGRAPHIC-CODE 4040 (reference FIG. 2) geographiccode 4465 from PAA-HOUSE-GEOGRAPHIC-CODE 4045 (reference FIG. 2) devicetype 4466 from PAA-VIDEO-VIEW-DEVICE-TYPE-CD 4050 (reference FIG. 2)

Claims Reference: This describes selecting the Histogram Bucket whoseranges envelop the Video Viewing Analysis Data Structure PlaybackDuration in Seconds and aggregating the Duration in Seconds into theselected Histogram Bucket.

The next step is to do Calculate Video Program Viewing 800 where theMeasurement Engine 200 calculates various metrics regarding VideoProgram Viewing. This is further explained in FIG. 16.

The next step is to Calculate Video Program Airing Viewing 850 where theMeasurement Engine 200 calculates various metrics regarding VideoProgram Airing Viewing. This is further explained in FIG. 18.

The next step is to Calculate Video Program Airing Segment Viewing 900where the Measurement Engine 200 calculates various metrics regardingVideo Program Segment Viewing. This is further explained in FIG. 20.

The next step is to check to see whether or not this is the Final Set ofRecords? 750. When Final Set of Records? Is true, the Measurement Engine200 proceeds to do a series of calculations as defined in CalculateSummary Viewing Statistics 960. Upon Completion of the variouscalculations, the Measurement Engine 200 writes the various result filesas per Write Output Files 760. At this point the processing is Done 765.

The detail of Load Viewing Activity to Data Structure 730 is explained.The reader is referred to the program code which is included herein byreference for additional details.

The Measurement Engine 200 reads the first record of Viewer InteractionData from the Video Viewing Event File 170 as per routineD000-PREP-DVR-REC-PB-EVENT-FIL. It saves the various identifying fields(Video Program Airing Id, House-Device-Viewer,Demographic-Geographic-Device Ids, and Session or Recording Playback Id)in the Video Viewing Analysis Data Structure (Ref FIG. 2) and in thesave fields.

Note: All of the viewing activity in the input file relates to one VideoProgram Id, so that field does not need to be saved.

Note: This embodiment supports processing of one kind of ViewingActivity Type (Linear, DVR, VOD) per run of the program. To processLinear, DVR, and VOD activity for the same Video Program requires threeseparate program runs with the corresponding data for the run type inthe Video Viewing Event File 170. An alternative embodiment couldsupport multiple Viewing Activity Types in one run.

In the mapping below, data from FIG. 15 is being used to populate FIG.2. The fields saved in the Video Viewing Analysis Data Structure (RefFIG. 2) with their mappings are:

Video Program Id—IN-VP-VIDEO-PROGRAM-ID 4105 or 4805 is loaded toPAA-VIDEO-PROGRAM-ID 4010

Video Program Airing Id—IN-VP-VIDEO-PROGRAM-AIRING-ID 4120 or 4820 isloaded to PAA-VIDEO-PROGRAM-AIRING-ID 4025

House Device Viewer—IN-HOUSE-DEVICE-VIEWER-ID 4122 or 4822 is loaded toPAA-HOUSE-DEVICE-VIEWER 4037

House Demographic Code—IN-HDVR-HOUSE-DEMOGRAPHIC-CODE 4125 or 4845 isloaded to PAA-HOUSE-DEMOGRAPHIC-CODE 4040

House Geographic Code—IN-HDVR-HOUSE-GEOGRAPHIC-CODE 4130 or 4850 isloaded to PAA-HOUSE-GEOGRAPHIC-CODE 4045

Viewing Device Type Code—IN-HDVR-VIDEO-VIEW-DEV-TYPE-CD 4135 or 4855 isloaded to PAA-VIDEO-VIEW-DEVICE-TYPE-CD 4050

Session Id or DVR Recording Playback Id or VOD SessionId—IN-DVR-RECORD-PLAYBACK-SESSION-ID 4140 or 4885 is loaded toPAA-RECORDING-PLAYBACK-SESSION-ID 4030

Other fields that are loaded to the array include:

Viewing Activity Type—IN-VIEWING-ACTIVITY-TYPE 4108 or 4808 is loaded toPAA-VIEWING_ACTIVITY_TYPE 4013

Video Program Duration in Seconds—IN-VP-DURATION-IN-SECONDS 4110 or 4810is loaded to PAA-VP-DURATION-IN-SECONDS 4015

Video Program Minimum Seconds for Exposure—IN-VP-MIN-SECS-FOR-EXPOSURE4115 or 4815 is loaded to PAA-VP-MIN-SECS-FOR-EXPOSURE 4020

Session Duration in Seconds or DVR Playback Duration or VOD PlaybackDuration IN-DRP-PLAYBACK-DURATN-IN-SECS 4145 or 4900 is loaded toPAA-PLAYBACK-DURATION-IN-SECS 4035

Video Viewing Analysis Data Structure Bucket Activity Field MappingNote: The following steps are explained in more detail below. This isthe field mapping.

Video Viewing Session Mode

IN-DRP-PLAYBACK-MODE-CODE 4150 or 4905 is loaded toPAA-PLAYBACK-SECOND-MODE 4060. Claims Reference: This is where theActivity Field Video Viewing Session Mode in the Video Viewing AnalysisData Structure Bucket is populated.

Video Viewing Session Volume Level

IN-DRP-PB-VOLUME-LEVEL-NUM 4165 or 4920 is loaded toPAA-SESSION-VOLUME-LEVEL 4065. Claims Reference: This is where theActivity Field Video Viewing Session Volume Level in the Video ViewingAnalysis Data Structure Bucket is populated.

Video Viewing Session Percent Content Visible

IN-DRP-PB-PCT-CONTENT-VISIBLE 4170 or 4925 is loaded toPAA-PERCENT-CONTENT-VISIBLE 4070.

Claims Reference: This is where the Activity Field Video Viewing SessionPercent Content Visible in the Video Viewing Analysis Data StructureBucket is populated.

Video Viewing Session Foreground Background Indicator

IN-DRP-PB-FOREGRD-BACKGRD-IND 4175 or 4930 is loaded toPAA-FOREGROUND-BACKGROUND-IND 4075.

Claims Reference: This is where the Activity Field Video Viewing SessionForeground Background Indicator in the Video Viewing Analysis DataStructure Bucket is populated.

Video Viewing Session Picture in Picture Indicator

IN-PICTURE-IN-PICTURE-IND 4185 or 4940 is loaded toPAA-PICTURE-IN-PICTURE-IND 4085.

Video Viewing Session Percent of Screen This Video

IN-PERCENT-OF-SCREEN-THIS-VIDEO 4190 or 4945 is loaded toPAA-PERCENT-OF-SCREEN-THIS-VIDEO 4090.

Claims Reference: This is where the Activity Field Video Viewing SessionPercent Of Screen This Video in the Video Viewing Analysis DataStructure Bucket is populated.

The system then performs a read loop on the remainder of the VideoViewing Event File 170 as per routine D100-PROCESS-DVR-REC-PB-EVENT.

In D100-PROCESS-DVR-REC-PB-EVENT, it first compares the input buffer tothe save fields. When they are the same, the system proceeds to analyzethe viewing activity represented in the record by running routineD110-PROC-DVR-REC-PB-ACTIVITY and various called routines.

The steps in D110-PROC-DVR-REC-PB-ACTIVITY in the program code are asfollows:

Session Processing

First, check to see if this is the start of a new session. Recall thatwithin one session there may be multiple events. When the record marks anew session (reference D114-FIRST-SESSION-EVT-ACTIONS), then using theIN-DRP-PLAYBACK-MODE-CODE 4150 or 4905, look up the playback modeDVR-PLAYBACK-MODE-CODE 4260 in the DVR-PLAYBACK-TALLY-RATE table (FIG.5-B) that was loaded as described in FIG. 4. This will provide the basetally rate DVR-PB-MODE-CODE-TALLY-RATE 4270 (FIG. 5-B) to be applied tothe viewing seconds represented in this Video Viewing Event record,except note that this rate may be reduced by the Playback Delay PenaltyFactor (see below). Each Playback mode has an associated tally rate. Forexample, in this embodiment, PL (Play) mode has a rate of 1 which isapplicable to Linear viewing and DVR playback in Play mode and VODviewing in Play mode. A second example is that F2 (fast forward at 2×speed) has a rate of perhaps 0.4. The analyst has the ability to definethe rate to be applied to each playback mode.

An alternative embodiment is to assign a value to the tally rate simplybecause the video content was being viewed or interacted with in someway.

Claims Reference: This relates to taking into account the video viewingsession mode in calculating the Viewer Interaction Score.

Claims Reference: By using the playback mode file as input to set thetally rate, the user is able to control the reference score associatedwith the video viewing session mode code.

Second (for this session), set the Playback Delay Penalty Factor. ForLinear viewing this is 1 as there is no delay. For DVR, there may be adelay from the time of recording to the time of viewing. The PlaybackDelay Penalty Factor (Ref FIG. 7-B) allows the analyst to reduce thevalue of viewing based on the amount of delay. The hours of delay isrecorded in field IN-HOURS-FROM-REC-TO-PLAYBACK 4180 (FIG. 15-A) or 4935(FIG. 15-B). This value is compared to the values inDVR-PLAYBACK-DELAY-PENALTY (Ref FIG. 7-B fields 4370 and 4380) to findthe corresponding row by comparing the hours of delay in viewing to theranges in that lookup table. The resulting factor PDP-PENALTY-RATE 4390will be applied to the Viewing Activity. For VOD, this value can beapplied as desired by the Analyst.

Claims Reference: This relates to taking into account the Playback delaypenalty factor in calculating the Viewer Interaction Score. In one case,a single penalty may be applied to all events. In another case, thepenalty may vary depending upon the amount of time between recording andplayback.

Using the Playback mode and its tally rate along with the Playback DelayPenalty Factor, calculate the base viewing points that will be appliedto each of the viewing seconds represented by the Session. This is theAdjusted Playback Mode Tally Rate and it is calculated by subtractingthe Playback Delay Penalty Factor from the Playback Mode Tally Rate thatwas looked up as such:

DVR-PB-MODE-CODE-TALLY-RATE 4270−PDP-PENALTY-RATE4390=PB-MODE-TALLY-RATE to be applied to each second of viewingactivity.

Once the tally rate is set, it is applied to all of the Session viewingseconds represented in the Video Viewing Event record (from File 170) bylooping thru the viewing seconds in the array based on usingIN-PB-MODE-BEG-SEC-FRM-TRU-BEG 4155 (for Linear) or 4910 (for DVR andVOD) to control the starting point and usingIN-PB-MODE-END-SEC-FRM-TRU-BEG 4160 (for Linear) or 4915 (for DVR andVOD) to control the ending point. For each second of the ViewingSession, the loop will populate the values of:

PAA-VIDEO-CONTENT-PART 4053 is populated with the part of the videocontent represented in the Bucket identifier using the loop subscript.

PAA-VIDEO-CONTENT-PART-ID 4054 is populated with video content partidentifier using the loop subscript.

PAA-PLAYBACK-SECOND-TALLY 4055 is populated with the tally amount.

PAA-PLAYBACK-SECOND-MODE 4060 is populated with the viewing mode code(‘PL’, ‘F1’, etc.)

By using the IN-PB-MODE-BEG-SEC-FRM-TRU-BEG 4155 or 4910 and theIN-PB-MODE-END-SEC-FRM-TRU-BEG 4160 or 4915 to set the viewing second inthe array, the Measurement Engine 200 is able to normalize the viewingacross all of the Linear viewing sessions and DVR playback sessions andVOD sessions, regardless of where in the session the user begins viewingor ends viewing or where in the session or DVR or VOD playback a trickplay is made to occur.

In the program the reader will also see logic related to the rank of theviewing activity which is used so that a lesser activity does notoverwrite a more valuable activity as would happen, if for example, aPlay activity was overwritten by a Fast Forward activity.

Event Processing Once the Session viewing activity value (Tally Rate) isset as described above, the Measurement Engine 200 will look for anyEvents that may reduce the value of the viewing activity. Such Eventsinclude Muting, Percent of Content Visible being reduced, Video inBackground, Picture-in-picture, and Multiple concurrent sessions(Percent of screen this video). Once the reductions from these eventsare calculated, they will be applied to the Playback Mode Tally Rate toreduce it. As a non-limiting example, a Session may span 30 minutes,within that Session, there may be any number of Events such as Muting orPicture-in-picture that the viewer has engaged in. These are theactivities that are being accounted for here. ReferenceD118-SET-ADJ-FCTRS-USING-EVNTS in the code for additional details. EachEvent has an associated Event Begin and End Second. For Linear (FIG.15-A), the Measurement Engine 200 uses EVENT-BEG-SEC-FROM-TRUE-BEG 4162and EVENT-END-SEC-FROM-TRUE-BEG 4163. For DVR and VOD (FIG. 15-B)Measurement Engine 200 uses EVENT-BEG-SEC-FROM-TRUE-BEG 4917 andEVENT-END-SEC-FROM-TRUE-BEG 4918.

At the start of Event processing, the Measurement Engine 200 sets up aloop using the EVENT-BEG-SEC-FROM-TRUE-BEG 4162 or 4917 andEVENT-END-SEC-FROM-TRUE-BEG 4163 or 4918 to control the Buckets on whichit performs Event processing. Recall that an Event will often occur as asubset of the overall Session, but the Event may span all the seconds ofthe Session.

Within the Event Loop, take these actions:

First, set the muting adjustment. This is based on the value recorded inIN-DRP-PB-VOLUME-LEVEL-NUM 4165 (FIG. 15-A) or 4920 (FIG. 15-B). Duringthe Loop process 4165 or 4920 is loaded to PAA-SESSION-VOLUME-LEVEL 4065(FIG. 2). The calculated Volume Adjustment, if any, is also set. This isused as follows: if the volume is zero (sound is on Mute), then thevalue of the viewing will be reduced. For example, perhaps 0.1 will bededucted from the viewing score when the volume is muted. For normalvolume ranges there is no deduction. The Volume Adjustment only appliesduring normal play mode, not during trick plays. In the presentembodiment this value is set in the program code based on business rulesin the code. Another embodiment may set the value using some othertechnique.

Claims Reference: This relates to taking into account the video viewingsession volume level in calculating the Viewer Interaction Score.

Second, set the content visible adjustment. This is based on the valuein IN-DRP-PB-PCT-CONTENT-VISIBLE 4170 (FIG. 15-A) or 4925 (FIG. 15-B).During the Loop process 4170 or 4925 is loaded toPAA-PERCENT-CONTENT-VISIBLE 4070 (FIG. 2). The Percent Content VisibleAdjustment, if any, is also set. This is used as follows: if the screenis occluded then the value of the viewing will be reduced by an amountdepending on how much of the screen is occluded with more occlusionresulting in a greater deduction. In the present embodiment this valueis set in the program code based on business rules in the code. Anotherembodiment may set the value using some other technique.

Claims Reference: This relates to taking into account the video viewingsession percent content visible in calculating the Viewer InteractionScore.

Third, set the picture-in-picture adjustment. This is based on the valuein IN-PICTURE-IN-PICTURE-IND 4185 (FIG. 15-A) or 4940 (FIG. 15-B).During the Loop process 4185 or 4940 is loaded toPAA-PICTURE-IN-PICTURE-IND 4085 (FIG. 2). The Picture In PictureAdjustment, if any, is also set. If the screen with this video contentis viewed in picture-in-picture mode, then the value of the viewing willbe reduced by the Picture In Picture Adjustment. In the presentembodiment this value is set in the program code based on business rulesin the code. Another embodiment may set the value using some othertechnique.

Fourth, set the foreground background adjustment. This is based on thevalue in IN-DRP-PB-FOREGRD-BACKGRD-IND 4175 (FIG. 15-A) or 4930 (FIG.15-B). During the Loop process 4175 or 4930 is loaded toPAA-FOREGROUND-BACKGROUND-IND 4075 (FIG. 2). The Foreground BackgroundAdjustment, if any, is also set. If the screen with the video contentbeing measured is in the background, then the value of the viewing willbe reduced by the Foreground Background Adjustment. In the presentembodiment this value is set in the program code based on business rulesin the code. Another embodiment may set the value using some othertechnique.

Claims Reference: This relates to taking into account the video viewingsession foreground background indicator in calculating the ViewerInteraction Score.

Fifth, set the percent of screen this video adjustment. This is based onthe value in IN-PERCENT-OF-SCREEN-THIS-VIDEO 4190 (FIG. 15-A) or 4945(FIG. 15-B). During the Loop process 4190 or 4945 is loaded toPAA-PERCENT-OF-SCREEN-THIS-VIDEO 4090 (FIG. 2). The Percent of Screen AdAdjustment, if any, is also set. If the viewer is watching multiplevideo programs on the screen (as in windows on a computer screen wouldoften be) then the value of the viewing will be reduced by an amountdepending on how much of the screen is used by this video with lessscreen space resulting in a reduced score. The value is the viewing willbe reduced by the Percent of Screen Adjustment. In the presentembodiment this value is set in the program code based on business rulesin the code. Another embodiment may set the value using some othertechnique.

Claims Reference: This relates to taking into account the video videoviewing session percent of screen this video in calculating the ViewerInteraction Score.

Once all these values are set, the Measurement Engine 200 will read thenext record the get the next Event for the Session. If there areadditional Events within the Session, then the Adjustment Factors forthose Events will be set. There are business rules in the code such thatsome events survive other events when they both occur during the samepart of the video content.

End Of Session Actions

When the last Event for the Session has been processed, then theMeasurement Engine 200 will perform end of session actions (referenceD120-END-OF-SESSION-ACTIONS). During this process the program loops thruall of the seconds of the viewing Session and applies the variousAdjustments to each of the Viewing seconds in the Session as needed. Inthis embodiment, the program will reduce the viewing score that wasoriginally applied to all of the viewing seconds in Session by applying(accounting for) the following values: Volume Adjustment, the PercentContent Visible Adjustment, the Picture In Picture Adjustment, theForeground Background Adjustment, and the Percent of Screen Adjustmentwhich were calculated for the viewing seconds related to each Event inthe Session. This is done by looping thru the buckets in the VideoViewing Analysis Data Structure (FIG. 2) based on the Session begin andend values that were originally defined fromIN-PB-MODE-BEG-SEC-FRM-TRU-BEG 4155 (for Linear) or 4910 (for DVR andVOD) to control the starting point and IN-PB-MODE-END-SEC-FRM-TRU-BEG4160 (for Linear) or 4915 (for DVR and VOD) to control the ending point.The loop will update the value of the PAA-PLAYBACK-SECOND-TALLY 4055based on the calculated Adjustments. In this embodiment, the Adjustmentsare subtracted from the viewing score.

After completing the routine D110-PROC-DVR-REC-PB-ACTIVITY, theMeasurement Engine 200 will resume processing by reading the next recordin the Video Viewing Event File 170. It then returns to the top of theD100-PROCESS-DVR-REC-PB-EVENT to begin the process again. When theMeasurement Engine 200 detects a change in the key, then it will proceedto write the Video Viewing Analysis Data File 783, Calculate HistogramViewing 785, then aggregate the second-by-second viewing activity forthe Video Program Viewing, the Video Program Airing Viewing, and theVideo Program Segment Viewing using the viewing activity informationthat was loaded to the Video Viewing Analysis Data Structure (Ref FIG.2) as described elsewhere in this specification.

Note that in this embodiment I have shown a strategy of subtracting thevarious Adjustments from the tally rate which was originally earnedduring the viewing second. Another embodiment may accomplish a similarresult using some other calculation methodology yet still fall withinthe scope of this teaching.

In the present embodiment, business rules are applied so that if thesame second has multiple viewing activities, the Play activity alwayssurvives (is not overridden by other activities). Multiple viewingactivities may occur when the Viewer uses forward and reverse featuresto view the same video content more than once. Another embodiment may beimplemented using different business rules to handle the case ofoverlapping viewing activities.

Business rules can be applied to determine, in the case of overlappingviewing activities such as Play, Reverse, Play, whether the totalviewing tally for the seconds involved may be greater than 1. The valuecan be capped at one, or a value greater than 1 may be allowed dependingon the business rules.

We now resume the discussion with Same Key? 725 having a value of No.

When the key in the record changes, then the Measurement Engine 200proceeds to step Write Viewing Analysis File 783. Reference FIG. 41 foran exemplary flowchart which describes the process for writing the VideoViewing Analysis File 205.

After step 783 the program proceeds to Calculate Histogram Viewing 785(reference code routine D140-TABULATE-HISTOGRAM), Calculate VideoProgram Viewing 800 (reference code routine E100-CALC-VIDEO-PGM-VIEWSand FIG. 16), Calculate Video Program Airing Viewing 850 (reference codeF100-CALC-VIDEO-PGM-AIR-VIEWS and FIG. 18), and calculate Video ProgramSegment Viewing 900 (reference code G100-CALC-VIDEO-PGM-AIR-SEG-VW andFIG. 20).

Once these steps are done, the Measurement Engine 200 is done working onviewing activity for that combination of Program Airing Id,Demographic-Geographic-Device group, and the Session/Playback id. Thesystem will then clear out the Video Viewing Analysis Data StructureFIG. 2 (reference DVR-REC-PLAYBACK-ACTIVITY-ANAL) in preparation forprocessing the viewing activity for the new key.

If there is a new record with a new key, code routineD110-PROC-DVR-REC-PB-ACTIVITY is executed as described previously toload that viewing activity to the Video Viewing Analysis Data StructureFIG. 2 (reference program code DVR-REC-PLAYBACK-ACTIVITY-ANAL).

If there are no further records because it is end of file on the VideoViewing Event File 170 (Final set of Records 750 is true), then theMeasurement Engine 200 proceeds to the final calculations as describedin Calculate Summary Viewing Statistics 960 FIG. 22 (referenceM100-FINAL-CALCULATIONS) and then to Write Output Files 760 as describedabove.

FIG. 15 relates to the Video Viewing Event File 170.

FIG. 15-A illustrates an exemplary record layout for Linear ViewingActivity—Video Viewing Event File 170 formatted for use as input to theMeasurement Engine 200, according to one embodiment. This file containsdetailed information about Linear viewing activity which will beanalyzed by the Measurement Engine 200.

FIG. 15-B illustrates an exemplary record layout for DVR and VOD ViewingActivity—Video Viewing Event File 170 formatted for use as input to theMeasurement Engine 200, according to one embodiment. This file containsdetailed information about DVR/VOD viewing activity which will beanalyzed by the Measurement Engine 200.

Note that the fields are named the same in both file formats so that thesame Measurement Engine 200 code can process both files. The Linearformat is populated with Viewer Interaction Data derived from Linearviewing activity including time-shifted linear viewing. The DVR/VODformat is populated with Viewer Interaction Data derived from DVR/VODviewing.

In one embodiment the Video Viewing Event File 170 is populated byquerying the Media Measurement Data Model. In an alternative embodimentthe Video Viewing Event File 170 can be populated from other sources.

Claims Reference: Linear Viewing Activity and DVR and VOD ViewingActivity are Viewer Interaction Data derived from a plurality of viewersinteracting with video content that was delivered on a plurality ofvideo asset viewing devices delivering content through a network.

FIG. 16 illustrates an exemplary flowchart for calculating Video ProgramViewing activity at a second-by-second level using data that has beenloaded to a Video Viewing Analysis Data Structure (Reference FIG. 2) inthe memory of a computer running the Measurement Engine 200. The videoprogram viewing can be the result of either a Linear Viewing Session, aDVR Playback Session, or a VOD play session. The Measurement Engine 200will calculate metrics using the data that has been loaded to this DataStructure.

The process begins with Calculate Video Program Viewing 800 (referenceE100-CALC-VIDEO-PGM-VIEWS and various called routines in the program).The Measurement Engine 200 executes Loop thru Demo-Geo-Device array 805(reference E140-CHECK-DEMO-GEO-DEVICE-KEY in program) which loops thruthe rows in the Video Program Viewing Activity data structure (referenceFIG. 17). More particularly, it is looping thru the occurrences ofDemographic—Geographic—Device to find a match between the values inVideo Viewing Analysis Data Structure (FIG. 2) and those in the VideoProgram Viewing Activity Data Structure (FIG. 17). The program executesDemo-Geo-Device key match found? 810. When no match is found, theprogram creates a row in the Video Program Viewing Activity DataStructure (FIG. 17) as per Create the Demo-Geo-Device key in VideoProgram array 820. After the row is created, processing continues. IfDemo-Geo-Device key match found? 810 is true and a match was found, thenthe program proceeds directly to Looping thru the playback activityarray performing calculations. This is done by Loop thru PlaybackActivity Array calculating Raw and Adjusted Video Program Values andAggregate Viewing Seconds for: Play mode, Skip Mode, Slow Play Mode,Forward 1×, 2×, 3×, 4×, Slow Reverse, Reverse 1×, 2×, 3×, 4× 825.

Claims Reference: This routine uses the Activity Field Video ViewingSession Mode in the Video Viewing Analysis Data Structure Bucket asinput to the calculations which create the Video Program ViewingMetrics.

Claims Reference: This routine uses the Activity Field ViewerInteraction Score in the Video Viewing Analysis Data Structure Bucket asinput to the calculations which create the Video Program ViewingMetrics.

Claims Reference: This routine is where Second-by-Second Video ProgramViewing Metrics are calculated.

In addition, the program also calculates the Viewing Device Count at asecond by second basis.

Next the program checks the beginning to end counts as per CalculateBeginning to End counts for PL, SK, SP, F1, F2, F3, F4, SR, R1, R2, R3,R4 830 where the Measurement Engine 200 is calculating the number ofsessions that were in the respective mode (PL, SK, etc.) for the entireduration of the session.

Claims Reference: This routine is where Program Level Video ProgramViewing Metrics are calculated.

Claims Reference: This routine is where Video Program Viewing Metricsare summarized from the second-by-second level to create Program LevelMetrics.

The next step is to calculate exposures per Calculate Exposures 835where the Measurement Engine 200 calculates the number of viewingsessions where the number of seconds in Play mode was sufficient toqualify as an exposure.

Claims Reference: This routine calculates the number of exposures intoan Exposures Count in the Video Program Viewing Activity Data Structure.

At the completion of this routine, all of the Viewer Interaction Datathat was loaded to the Video Viewing Analysis Data Structure has beenprocessed to the Video Program Viewing Activity Data Structure. Theprogram is Done 840 calculating Video Program Metrics.

Claims Reference: FIG. 16 describes performing calculations using thevalues in the Video Viewing Analysis Data Structure Buckets to createVideo Program Viewing Metrics.

Details for Demo-Geo-Device Key Match Found? 810

The identifying fields are compared to find a match between the VideoViewing Analysis Data Structure (FIG. 2) and those in the Video ProgramViewing Activity Data Structure (FIG. 17) are as follows:

House Demographic Code PAA-HOUSE-DEMOGRAPHIC-CODE 4040 andVP-HOUSE-DEMOGRAPHIC-CODE 5036

House Geographic Code PAA-HOUSE-GEOGRAPHIC-CODE 4045 andVP-HOUSE-GEOGRAPHIC-CODE 5038 Video Viewing Device Type CodePAA-VIDEO-VIEW-DEVICE-TYPE-CD 4050 and VP-VIDEO-VIEW-DEVICE-TYPE-CD5042.

FIG. 17 illustrates an exemplary data structure used for CalculatingVideo Program Viewing Activity in the memory of a computer, according toone embodiment. The Video Program Viewing Activity Data Structure isused in calculating the Video Program level metrics. These metricsrelate to the viewing activity across all of the viewings from thevarious airings of the program.

When the Viewing Activity Type 5014 is “DVR”, then this data structureis recording Digital Video Recording viewing activity (viewing activitythat is based on the playback with trick modes, etc.) of a Digital VideoRecording.

When the Viewing Activity Type 5014 is “VOD”, then this data structureis recording Video On Demand viewing activity.

When the Viewing Activity Type 5014 is “LIN”, then this data structureis recording Linear viewing activity.

The Demographic-Geographic-Device information is used to group ViewingActivity of the program by Demographic Geographic and Devicecombinations.

Claims Reference: In FIG. 17 fields 5010 to 5042 are Video ProgramViewing Identifying Fields

Claims Reference: In FIG. 17 fields 5046 to 5246 are Video ProgramViewing Activity Fields which includes both Program Level metrics andSecond-by-Second metrics

Claim Reference: by putting the Video Program Viewing Activity Fields inthe same Data Structure as child members to the Video Program ViewingIdentifying Fields, this creates the correlation between the Identifyingfields and the Activity Fields.

FIG. 18 illustrates an exemplary flowchart for calculating Video ProgramAiring Viewing activity at a second-by-second level using data that hasbeen loaded to a Video Viewing Analysis Data Structure (Reference FIG.2) in the memory of a computer running the Measurement Engine 200. Thevideo program airing viewing can be the result of either a LinearViewing Session, a DVR Playback Session, or a VOD play session. TheMeasurement Engine 200 will calculate metrics using the data that hasbeen loaded to this Data Structure.

The process begins with Calculate Video Program Airing Viewing 850(reference F100-CALC-VIDEO-PGM-AIR-VIEWS and various called routines inthe program). The Measurement Engine 200 executes Loop thru VideoProgram Airing array to find matching airing row 855 (referenceF140-CHK-VIDEO-PROG-AIRING-ID in program) which loops thru the rows inthe Video Program Airing Viewing Activity data structure (reference FIG.19). After finding the matching video program airing, the MeasurementEngine 200 executes Loop thru Demo-Geo-Device array 860 (referenceF240-CHK-DEMO-GEO-DEVICE-KEY in program) which loops thru the rows inthe Video Program Airing Viewing Activity Data Structure (reference FIG.19). More particularly, it is looping thru the occurrences ofDemographic—Geographic—Device to find a match between the values inVideo Viewing Analysis Data Structure (FIG. 2) and those in the VideoProgram Airing Viewing Activity Data Structure (FIG. 19). The programexecutes Demo-Geo-Device key match found? 865. When no match is found,the program creates a row in the Video Program Airing

Viewing Activity Data Structure (FIG. 19) as per Create theDemo-Geo-Device key in Video Program Airing array 870. After the row iscreated, processing continues. If Demo-Geo-Device key match found? 865is true and a match was found, then the program proceeds directly toLooping thru the playback activity array calculating the values. This isdone by Loop thru Playback Activity Array calculating Raw and AdjustedVideo Program Airing Values and Aggregate Viewing Seconds for: Playmode, Skip Mode, Slow Play Mode, Forward 1×, 2×, 3×, 4× Slow Reverse,Reverse 1×, 2×, 3×, 4× 875.

Claims Reference: This routine uses the Activity Field Video ViewingSession Mode in the Video Viewing Analysis Data Structure Bucket asinput to the calculations which create the Video Program Airing ViewingMetrics.

Claims Reference: This routine uses the Activity Field ViewerInteraction Score in the Video Viewing Analysis Data Structure Bucket asinput to the calculations which create the Video Program Airing ViewingMetrics.

Claims Reference: This routine is where Second-by-Second Video ProgramAiring Viewing

Metrics are calculated.

In addition, the program also calculates the Viewing Device Count at asecond by second basis.

Next the program creates the beginning to end counts as per CalculateBeginning to End counts for PL, SK, SP, F1, F2, F3, F4, SR, R1, R2, R3,R4 880 where the Measurement Engine 200 is calculating the number ofsessions that were in the respective mode (PL, SK, etc.) for the entireduration of the session.

Claims Reference: This routine is where Program Airing Level VideoProgram Airing Viewing Metrics are calculated.

Claims Reference: This routine is where Video Program Airing ViewingMetrics are summarized from the second-by-second level to create ProgramAiring Level Metrics.

The next step is to calculate exposures per Calculate Exposures 885where the Measurement Engine 200 calculates the number of viewingsessions where the number of seconds in Play mode was sufficient toqualify as an exposure.

At the completion of this routine, all of the Viewer Interaction Datathat was loaded to the Video Viewing Analysis Data Structure has beenprocessed to the Video Program Airing Viewing Activity Data Structure.The program is Done 890 calculating Video Program Airing Metrics.

Claims Reference: FIG. 18 describes performing calculations using thevalues in the Video Viewing Analysis Data Structure Buckets to createVideo Program Airing Viewing Metrics.

Details for Demo-Geo-Device Key Match Found? 865

The identifying fields are compared to find a match between the VideoViewing Analysis Data Structure (FIG. 2) and those in the Video ProgramAiring Viewing Activity Data Structure (FIG. 19) are as follows:

House Demographic Code PAA-HOUSE-DEMOGRAPHIC-CODE 4040 andVPA-HOUSE-DEMOGRAPHIC-CODE 5436

House Geographic Code PAA-HOUSE-GEOGRAPHIC-CODE 4045 andVPA-HOUSE-GEOGRAPHIC-CODE 5438

Video Viewing Device Type Code PAA-VIDEO-VIEW-DEVICE-TYPE-CD 4050 andVPA-VIDEO-VIEW-DEVICE-TYPE-CD 5442.

FIG. 19 illustrates an exemplary Video Program Airing Data Structureused for Calculating Video Program Airing Viewing Activity in the memoryof a computer, according to one embodiment.

The Video Program Airing Data Structure is used in calculating the VideoProgram Airing level metrics. These metrics relate to all of the viewingactivity for each airing of the program and associated viewings. Byanalyzing viewing at the individual airing level for a program, theMeasurement Engine 200 is able to provide metrics related to viewing foreach airing. This can be useful in determining whether or not there aresufficient viewers of an airing to make it worth showing. Also,advertising rates can be set accordingly when viewership is known at theairing level.

Viewing Activity Type

When the Viewing Activity Type 5412 is “DVR”, then this record isrecording Digital Video Recording viewing activity (viewing activitythat is based on the playback with trick modes, etc.) of a Digital VideoRecording.

When the Viewing Activity Type 5412 is “VOD”, then this record isrecording Video On Demand viewing activity.

When the Viewing Activity Type 5412 is “LIN”, then this record isrecording Linear viewing activity.

The Demographic-Geographic-Device information is used to group ViewingActivity of the program airing by Demographic Geographic and Devicecombinations.

Claims Reference: In FIG. 19 fields 5410 to 5442 are Video ProgramAiring Viewing Identifying Fields

Claims Reference: In FIG. 19 fields 5446 to 5646 are Video ProgramAiring Viewing Activity Fields which includes both Program Airing Levelmetrics and Second-by-Second metrics.

Claim Reference: by putting the Video Program Airing Viewing ActivityFields in the same Data Structure as child members to the Video ProgramAiring Viewing Identifying Fields, this creates the correlation betweenthe Identifying fields and the Activity Fields.

FIG. 20 illustrates an exemplary flowchart for calculating Video ProgramSegment Viewing activity at a second-by-second level using data that hasbeen loaded to a Video Viewing Analysis Data Structure (Reference FIG.2) in the memory of a computer running the Measurement Engine 200. Thevideo program airing segment viewing can be the result of either aLinear Viewing Session, a DVR Playback Session, or a VOD play session.The Measurement Engine 200 will aggregate the data that has been loadedto this Data Structure.

The process begins with Calculate Video Program Airing Segment Viewing900 (reference G100-CALC-VIDEO-PGM-AIR-SEG-VW and various calledroutines in the program). The Measurement Engine 200 executes Loop thruVideo Program Airing array to find matching airing row 905 (referenceG140-CHK-VIDEO-PGM-AIR-SEG in program) which loops thru the rows in theVideo Program Airing Segment Viewing Activity Data Structure (ref FIG.21) to find the matching video program airing. After finding thematching video program airing, the Measurement Engine 200 executes Loopthru Video Program Airing Segment array 910 (referenceG200-VIDEO-PGM-AIR-SEG and G240-CHK-VIDEO-PGM-AIR-SEG in program) whichloops thru the rows in the Video Program Airing Segment Viewing ActivityData Structure (reference FIG. 21).

After finding the matching video program segment (within the VideoProgram airing), the Measurement Engine 200 executes Loop thruDemo-Geo-Device array within Video Program Airing Segment 915 (referenceG300-TALLY-VIDEO-PGM-AIR-SEG and G340-CHK-VIDEO-PGM-AIR-SEG in program)which loops thru the rows in the Video Program Airing Segment ViewingActivity Data Structure (reference FIG. 21). More particularly, it islooping thru the occurrences of Demographic—Geographic—Device to find amatch between the values in Video Viewing Analysis Data Structure (FIG.2) and those in the Video Program Airing Segment Viewing Activity datastructure (FIG. 21). The program executes Demo-Geo-Device key matchfound within Segment? 920. When no match is found, the program creates arow in the Video Program Airing Segment Viewing Activity Data Structure(FIG. 21) as per Create the Demo-Geo-Device key in Video Program AiringSegment array 925 (reference G340-CHK-VIDEO-PGM-AIR-SEG in program).After the row is created, processing continues. If Demo-Geo-Device keymatch found within Segment? 920 is true and a match was found, then theprogram proceeds directly to Looping thru the playback activity arrayperforming calculations. This is done by Loop thru Playback ActivityArray calculating Video Program Airing Segment Raw and Adjusted VideoProgram Values and Aggregate Viewing Seconds for this Demo-Geo-Device:Play mode, Skip Mode, Slow Play Mode, Forward 1×, 2×, 3×, 4×, SlowReverse, Reverse 1×, 2×, 3×, 4× 930.

Claims Reference: This routine uses the Activity Field Video ViewingSession Mode in the Video Viewing Analysis Data Structure Bucket asinput to the calculations which create the Video Program Airing SegmentViewing Metrics.

Claims Reference: This routine uses the Activity Field ViewerInteraction Score in the Video Viewing Analysis Data Structure Bucket asinput to the calculations which create the Video Program Airing SegmentViewing Metrics.

Claims Reference: This routine is where Second-by-Second Video ProgramAiring Segment Viewing Metrics are calculated.

In addition, the program also calculates the Viewing Device Count at asecond by second basis.

Next the program creates the beginning to end counts as per CalculateBeginning to End counts for PL, SK, SP, F1, F2, F3, F4, SR, R1, R2, R3,R4 935 where the Measurement Engine 200 is calculating the number ofsessions that were in the respective mode (PL, SK, etc.) for the entireduration of the segment.

Claims Reference: This routine is where Program Airing Segment LevelVideo Program Airing Segment Viewing Metrics are calculated.

Claims Reference: This routine is where Video Program Airing SegmentViewing Metrics are summarized from the second-by-second level to createProgram Airing Segment Level Metrics.

The next step is to calculate exposures per Calculate Exposures 940where the Measurement Engine 200 calculates the number of viewingsessions where the number of seconds in Play mode was sufficient toqualify as an exposure.

Claims Reference: This routine calculates the number of exposures intoan Exposures Count in said Video Program Airing Segment Viewing ActivityData Structure.

At the completion of this routine, all of the Viewer Interaction Datathat was loaded to the Video Viewing Analysis Data Structure has beenprocessed to the Video Program Airing Segment Viewing Activity DataStructure. The program is Done 950 calculating Video Program AiringSegment Metrics.

Claims Reference: FIG. 20 describes performing calculations using thevalues in said Video Viewing Analysis Data Structure Buckets to createVideo Program Airing Segment Viewing Metrics.

Details for Demo-Geo-Device key match found? 920

The identifying fields are compared to find a match between the VideoViewing Analysis Data Structure (FIG. 2) and those in the Video ProgramAiring Segment Viewing Activity Data Structure (FIG. 21) are as follows:

House Demographic Code PAA-HOUSE-DEMOGRAPHIC-CODE 4040 andVPAS-HOUSE-DEMOGRAPHIC-CODE 5836

House Geographic Code PAA-HOUSE-GEOGRAPHIC-CODE 4045 andVPAS-HOUSE-GEOGRAPHIC-CODE 5838

Video Viewing Device Type Code PAA-VIDEO-VIEW-DEVICE-TYPE-CD 4050 andVPAS-VIDEO-VIEW-DEVICE-TYPE-CD 5842.

FIG. 21 illustrates an exemplary Video Program Airing Segment DataStructure used for Calculating Video Program Airing Segment ViewingActivity in the memory of a computer, according to one embodiment.

The Video Program Airing Segment Data Structure is used in calculatingthe Video Program Airing Segment level metrics. These metrics relate toall of the viewing activity for each segment in each airing of theprogram and associated viewings. This data allows the Analyst to analyzeviewing against a segment that aired during a certain airing of aprogram. A segment may define a commercial break or any other programpart. By analyzing viewing at the segment level for the individualairing level for a program, the Measurement Engine 200 is able toprovide metrics related to segment level viewing for each airing. Recallthat the Analyst can define multiple segments for a video program. Asegment may define a commercial break. By tracking segment levelviewing, the Measurement Engine 200 is able to collect viewingstatistics for the various ads that ran during each airing of theprogram for Linear viewing sessions, or a DVR playback sessions, or aVOD sessions.

The segment definitions are read from the input file Video ProgramSegment File 160 (Reference FIG. 12) and then copied to each airing ofthe program in the Video Program Airing Segment Viewing Activity DataStructure (FIG. 21) at the start of processing (reference routineC146-COPY-SEG-DATA-TO-PGM-AIR).

The Demographic-Geographic-Device information is used to group ViewingActivity of the aired segment of the program by Demographic Geographicand Device combinations. As a nonlimiting example of how thisinformation can be used, if the segment defines an ad break in theprogram, and if the same program airs at 5:00 PM and 9:00 PM, theMeasurement Engine 200 can provide viewership counts of the ad from the5:00 PM airing and from the 9:00 PM airing. This can be useful indetermining whether or not it makes sense to run an ad during each ofthose airing times. Additionally, because the Measurement Engine 200 istracking Demographic information about the viewer, the Analyst candetermine which ad to place during each airing based on the demographicsof the viewers. Similarly, if there are geographically based adplacements, by knowing the viewership by geographic area, the Analystcan determine where to direct the ad placement. By knowing viewership bydevice characteristic, the Analyst can determine when to place an ad ifhe desires to reach users that view content using a certain device typesuch as a tablet vs. a STB with television.

In all of these examples, advertising rates can be set according to theviewership information.

Viewing Activity Type

When the Viewing Activity Type 5812 is “DVR”, then this record isrecording Digital Video Recording viewing activity (viewing activitythat is based on the playback with trick modes, etc.) of a Digital VideoRecording.

When the Viewing Activity Type 5812 is “VOD”, then this record isrecording Video On Demand viewing activity.

When the Viewing Activity Type 5812 is “LIN”, then this record isrecording Linear viewing activity.

The Demographic-Geographic-Device information is used to group ViewingActivity of the program airing segment by Demographic Geographic andDevice combinations.

Claims Reference: In FIG. 21 fields 5810 to 5842 are Video ProgramAiring Segment Viewing Identifying Fields

Claims Reference: In FIG. 21 fields 5846 to 6046 are Video ProgramAiring Segment Viewing Activity Fields which includes both Program Levelmetrics and Second-by-Second metrics.

Claim Reference: by putting the Video Program Airing Segment ViewingActivity Fields in the same Data Structure as child members to the VideoProgram Airing Segment Viewing

Identifying Fields, this creates the correlation between the IdentifyingFields and the Activity Fields.

FIG. 22 illustrates an exemplary flowchart for calculating the SummaryViewing Statistics. These statistics are calculated on three levels: (1)the Video Program level, (2) the Video Program Airing level, and (3) theVideo Program Airing Segment level. At each level the Measurement Engine200 is calculating various values that span the details in therespective Data Structures.

The process begins with Calculate Summary Viewing Statistics 960. Thefirst step is Calculate Video Program Statistics 965 in which thefollowing actions take place:

Loop Thru Demo-Geo-Devices for Video Program

-   -   Calculate Video Program Demo-Geo-Device Aggregate Adjusted        Viewing Seconds Loop thru Seconds for Video Program        Demo-Geo-Device        -   Calculate Video Program Demo-Geo-Device per second Adjusted            Viewing Count        -   Calculate Video Program Demo-Geo-Device per second Raw            Viewing Count

To recap, in this step the Measurement Engine 200 loops thru all of theDemo-Geo-Device combinations for this Video Program and calculates theAggregate Adjusted Viewing Seconds. The aggregate adjusted viewingseconds is the sum of all the aggregate viewing seconds of each playbackmode (PL, SK, SP, F1, etc.) for this Demo-Geo-Device in the context ofthis Video Program.

Once this part is complete, the program will then loop thru the viewingseconds and calculate the adjusted viewing count and the raw viewingcount. The Adjusted total viewing count is the sum across all theseconds of the adjusted PL, SK, SP, F1, etc. counts. The Raw totalviewing count is the sum across all the seconds of the Raw PL, SK, SP,F1, etc. counts. Reference M100-FINAL-CALCULATIONS for the program code.

The process then continues with Calculate Video Program AiringStatistics 970 in which the following actions take place.:

Loop thru Video Program Airings

-   -   Loop thru Demo-Geo-Devices for Video Program Airing        -   Calculate Video Program Airing Demo-Geo-Device Aggregate            Adjusted Viewing Seconds Loop thru Seconds for Video Program            Airing Demo-Geo-Device            -   Calculate Video Program Airing Demo-Geo-Device per                second Adjusted Viewing Count            -   Calculate Video Program Airing Demo-Geo-Device per                second Raw Viewing Count

To recap, in this step the Measurement Engine 200 loops thru each of theProgram Airings and then for each Airing, it loops thru all of theDemo-Geo-Device combinations for this Video Program Airing andcalculates the Aggregate Adjusted Viewing Seconds at the Program Airinglevel. The aggregate adjusted viewing seconds is the sum of all theaggregate viewing seconds of each playback mode (PL, SK, SP, F1, etc.)for this Demo-Geo-Device in the context of this Program Airing.

Once this part is complete, the program will then loop thru the viewingseconds and calculate the adjusted viewing count and the raw viewingcount for this Demo-Geo-Device in the context of this Program Airing.The Adjusted total viewing count is the sum across all the seconds ofthe adjusted PL, SK, SP, F1, etc. counts. The Raw total viewing count isthe sum across all the seconds of the Raw PL, SK, SP, F1, etc. counts.Reference M100-FINAL-CALCULATIONS for the program code.

The process then continues with Calculate Video Program Airing SegmentStatistics 975 in which the following actions take place.:

Loop thru Video Program Airings

-   -   Loop thru Video Program Airing Segments        -   Loop thru Demo-Geo-Devices for Video Program Airing Segment            -   Calculate Video Program Airing Segment Demo-Geo-Device                Aggregate Adjusted Viewing Seconds            -   Loop thru Seconds for Video Program Airing Segment                Demo-Geo-Device                -   Calculate Video Program Airing Segment                    Demo-Geo-Device per second Adjusted Viewing Count                -   Calculate Video Program Airing Segment                    Demo-Geo-Device per second Raw Viewing Count

To recap, in this step the Measurement Engine 200 loops thru each of theProgram Airings and then for each Airing, it loops thru all of theProgram Airing Segments and then for each Segment it loops thru all ofthe Demo-Geo-Device combinations for this Video Program Airing Segmentand calculates the Aggregate Adjusted Viewing Seconds at the ProgramAiring Segment level. The aggregate adjusted viewing seconds is the sumof all the aggregate viewing seconds of each playback mode (PL, SK, SP,F1, etc.) for this Demo-Geo-Device in the context of the Program Segmentin the context of the Program Airing.

Once this part is complete, the program will then loop thru the viewingseconds and calculate the adjusted viewing count and the raw viewingcount for this Demo-Geo-Device in the context of this Program Segment inthe context of this Program Airing. The Adjusted total viewing count isthe sum across all the seconds of the Adjusted PL, SK, SP, F1, etc.counts. The Raw total viewing count is the sum across all the seconds ofthe Raw PL, SK, SP, F1, etc. counts. Reference M100-FINAL-CALCULATIONSfor the program code.

After step 975 is complete, the program is done Done 980 with thecalculation of summary viewing statistics.

Ready to Write Output Files

At this point, the Measurement Engine 200 has completed all of thecalculations and it is now ready to create the output files. Creation ofthe output files is discussed in FIGS. 23 to 31. In the program routineX100-WRITE-DVR-REC-PB-STATS controls the writing of the output files.

Note to the reader: As read the program source code, you will see thatfor each output file, the Measurement Engine 200 has the ability towrite the file in either pipe delimited format or in commas separatedvalue format.

FIG. 23 illustrates an exemplary flowchart for writing the summarystatistics related to the entire run. The process begins with WriteViewing Statistics 9110. The Measurement Engine 200 then formats therecord and writes the file per step Write Video Program ViewingStatistics 9120 which writes file Viewing Statistics File 210. Therecord layout for this file is described in FIG. 32.

Reference X100-WRITE-DVR-REC-PB-STATS for the program code.

FIG. 24 illustrates an exemplary flowchart for writing the viewinghistogram data for the entire run. The process begins with Write ViewingHistogram 9210. The Measurement Engine 200 then proceeds to WriteViewing Histogram 9220 where it does the following:

Loop thru rows in Histogram Data Structure

Format record from data in Histogram Data Structure

Write record to file

Step 9220 writes file Viewing Histogram File 220. The record layout forthis file is described in FIG. 33.

When all of the histogram rows have been written to the file, theprocess is done.

Reference X200-WRITE-DVR-REC-PB-HISTG for the program code.

FIG. 25 illustrates an exemplary flowchart for writing the Video ProgramDemo-Geo-Device level results for the entire run. The process beginswith Write Viewing Program Demo-Geo-Device Viewing Results 9310. TheMeasurement Engine 200 then proceeds to Write Video ProgramDemo-Geo-Device Viewing Results 9320 where it does the following:

Loop thru Demo-Geo-Devices for Video Program

Format record from data in Video Program Array Data Structure

Write record to file

Step 9320 writes file Video Program Demo-Geo-Device Viewing File 230.The record layout for this file is described in FIG. 34.

When all of the Video Program Demo-Geo-Device have been written to thefile, the process is done.

Reference X300-WRITE-VID-PGM-DEM-GEO-DEV for the program code.

FIG. 26 illustrates an exemplary flowchart for writing the Video ProgramDemo-Geo-Device activity at a second-by-second level for the entire run.The process begins with Write Video Program Viewing Activity by SecondResults 9410. The Measurement Engine 200 then proceeds to Write VideoProgram Viewing Activity by Second Results 9420 where it does thefollowing:

Loop thru Demo-Geo-Devices for Video Program

-   -   Loop thru the Viewing Second    -   Format record from data in Video Program Array Second-by-second        Detail Data Structure    -   Write record to file

Step 9420 writes file Video Program Viewing Activity by Second File 240.The record layout for this file is described in FIG. 35.

When all of the Video Program Demo-Geo-Device second-by-second activityhas been written to the file, the process is done.

Reference X400-WRITE-VID-PGM-VW-ACT-BY-S for the program code.

FIG. 27 illustrates an exemplary flowchart for writing the Video ProgramAiring Demo-Geo-Device level results for the entire run. The processbegins with Write Viewing Program Airing Demo-Geo-Device Viewing Results9510. The Measurement Engine 200 then proceeds to Write Video ProgramAiring Demo-Geo-Device Viewing Results 9520 where it does the following:

Loop thru Video Program Airing rows in Video Program Airing Array

-   -   Loop thru Demo-Geo-Devices for Video Program Airing    -   Format record from data in Video Program Airing Array Data        Structure    -   Write record to file

Step 9520 writes file Video Program Airing Demo-Geo-Device Viewing File250. The record layout for this file is described in FIG. 36.

When all of the Video Program Airing Demo-Geo-Device data has beenwritten to the file, the process is done.

Reference X500-WRITE-VIDEO-PGM-AIR-DGD for the program code.

FIG. 28 illustrates an exemplary flowchart for writing the Video ProgramAiring Demo-Geo-Device activity at a second-by-second level for theentire run. The process begins with Write Video Program Airing ViewingActivity by Second Results 9610. The Measurement Engine 200 thenproceeds to Write Video Program Airing Viewing Activity by SecondResults 9620 where it does the following:

Loop thru Video Program Airing rows in Video Program Airing Array

-   -   Loop thru Demo-Geo-Devices for Video Program Airing        -   Loop thru the Viewing Second of Video Program Airing        -   Format record from data in Video Program Airing Array            Second-by-second            -   Detail Data Structure        -   Write record to file

Step 9620 writes file Video Program Airing Viewing Activity by SecondFile 260. The record layout for this file is described in FIG. 37.

When all of the Video Program Airing Demo-Geo-Device second-by-secondactivity has been written to the file, the process is done.

Reference X600-WRITE-VIDEO-PGM-AIR-VABS for the program code.

FIG. 29 illustrates an exemplary flowchart for writing the Video ProgramAiring Segment Header data for each Video Program Airing Segment thatwas processed during the run. The process begins with Write ViewingProgram Airing Segment Header 9710. The Measurement Engine 200 thenproceeds to Write Viewing Program Airing Segment Header 9720 where itdoes the following:

Loop thru Video Program Airing rows in Video Program Airing SegmentArray

-   -   Loop thru Segments in the Video Program Airing Segment Array    -   Format record from data in Video Program Airing Segment Array        Data Structure    -   Write record to file

Step 9720 writes file Video Program Airing Segment File 270. The recordlayout for this file is described in FIG. 38.

When all of the Program Airing Segment Header data has been written tothe file, the process is done.

Reference X700-WRITE-VIDEO-PGM-AIR-SEG for the program code.

FIG. 30 illustrates an exemplary flowchart for writing the Video ProgramAiring Segment Demo-Geo-Device level results for the entire run. Theprocess begins with Write Viewing Program Airing Segment Demo-Geo-DeviceViewing Results 9810. The Measurement Engine 200 then proceeds to WriteVideo Program Airing Demo-Geo-Device Viewing Results 9820 where it doesthe following:

Loop thru Video Program Airing rows in Video Program Airing SegmentArray

-   -   Loop thru Video Program Airing Segment rows in Video Program        Airing Segment Array        -   Loop thru Demo-Geo-Devices for Video Program Airing Segment        -   Format record from data in Video Program Airing Segment            Array Data Structure    -   Write record to file

Step 9820 writes file Video Program Airing Segment Demo-Geo-DeviceViewing File 280. The record layout for this file is described in FIG.39.

When all of the Video Program Airing Segment Demo-Geo-Device data hasbeen written to the file, the process is done.

Reference X800-VIDEO-PGM-AIR-SEGMENT for the program code.

FIG. 31 illustrates an exemplary flowchart for writing the Video ProgramAiring Segment viewing activity at a second-by-second level for theentire run. The process begins with Write Video Program Airing SegmentViewing Activity by Second Results 9910. The Measurement Engine 200 thenproceeds to Write Video Program Airing Segment Viewing Activity bySecond Results 9920 where it does the following:

Loop thru Video Program Airing rows in Video Program Airing SegmentArray

-   -   Loop thru Video Program Airing Segment rows in Video Program        Airing Segment Array        -   Loop thru Demo-Geo-Device row for Video Program Airing            Segment            -   Loop thru Viewing Second rows for Video Program Airing                Segment            -   Format record from data in Video Program Airing Array                Second-by-second Detail Data Structure        -   Write record to file

Step 9920 writes file Video Program Airing Segment Viewing Activity bySecond File 290. The record layout for this file is described in FIG.40.

-   -   When all of the Video Program Airing Segment second-by-second        activity has been written to the file, the process is done.

Reference X900-WRITE-VID-PGM-AIR-SEG-DGD for the program code.

Review of FIGS. 32-40.

I will now review FIGS. 32-40.

These figures provide the record layouts for the various files that arecreated by the Measurement Engine 200 as a result of calculating videoasset viewing activity. These files are structured such that they can beloaded to a database where a reporting application can be developed. Toassist the reader in implementing such a system I have providedsuggested Table names. I have also indicated the Parent table name toshow how each table fits within the context of a Media Measurement DataModel. The reader will note that while this embodiment shows that theseoutputs are created as flat files, another embodiment may insert to orupdate a data base table to record this information. Yet anotherembodiment may show XML messages or any other computer readable format.

The reader will find a block of information entitled Summary Informationfor each of FIGS. 32-40. It provides a Short name of the file/data, aTable Name which is a suggested name which can be assigned to the tableto which this file is loaded in the database, a Parent table name in thecontext of a Media Measurement Data Model, the Output file name assignedby Measurement Engine 200, a Record description, and the SpecificationFile Name. With these various elements, the reader has anstart-to-finish view of each file.

After the Summary Information, the reader will find the Record Layoutwhich lists the individual fields, data type, size, and description ordefinition for each field in the file.

For each file, in the DESCRIPTION field under the Record Layout, I havespecified how the field is populated or where the field is populatedfrom. Additionally, because the source field contains the definition Ihave not included it the record layouts in FIGS. 32-40.

FIG. 32 illustrates summary information and an exemplary record layoutfor the Viewing Statistics file 210 which is produced by the MeasurementEngine 200 as a result of calculating video asset viewing activity.

FIG. 33 illustrates summary information and an exemplary record layoutfor the Viewing Histogram file 220 which are produced by the MeasurementEngine 200 as a result of calculating video program viewing activity.

FIG. 34 illustrates summary information and an exemplary record layoutfor the Video Program Demographic Geographic Device Viewing file 230which are produced by the Measurement Engine 200 as a result ofcalculating video program viewing activity.

FIG. 35 illustrates summary information and an exemplary record layoutfor the Video Program Viewing Activity by Second file 240 which areproduced by the Measurement Engine 200 as a result of calculating videoprogram viewing activity.

FIG. 36 illustrates summary information and an exemplary record layoutfor the Video Program Airing Demographic Geographic Device Viewing file250 which are produced by the Measurement Engine 200 as a result ofcalculating video program viewing activity.

FIG. 37 illustrates summary information and an exemplary record layoutfor the Viewing Program Airing Viewing Activity by Second file 260 whichare produced by the Measurement Engine 200 as a result of calculatingvideo program viewing activity.

FIG. 38 illustrates summary information and an exemplary record layoutfor the Video Program Airing Segment file 270 which are produced by theMeasurement Engine 200 as a result of calculating video program viewingactivity.

FIG. 39 illustrates summary information and an exemplary record layoutfor the Video Program Airing Segment Demographic Geographic Device file280 which are produced by the Measurement Engine 200 as a result ofcalculating video program viewing activity.

FIG. 40 illustrates summary information and an exemplary record layoutfor the Video Program Airing Segment Viewing Activity by Second file 290which are produced by the Measurement Engine 200 as a result ofcalculating video program viewing activity.

FIG. 41 illustrates an exemplary flowchart which describes the processfor writing the Video Viewing Analysis File 205. The process maps thefields in the Video Viewing Analysis Data Structure (FIG. 2) to therecord layout in FIG. 41 and then it writes the record. As part of theprocess the system loops through the Video Viewing Analysis DataStructure Buckets and writes one record for each Bucket that has viewingactivity represented in it.

The process begins with Write Video Viewing Analysis File 9940. Itcontinues to Write Video Viewing Analysis Results 9942 where it Loopsthru Video Viewing Analysis Data Structure Buckets, Formats the outputrecord FIG. 42 from data in Video Viewing Analysis Data Structure (FIG.2), and then Writes the record to file thus creating Video ViewingAnalysis File 205. The process is done when it has looped thru all theBuckets in the Video Viewing Analysis Data Structure (FIG. 2).

FIG. 42 illustrates an exemplary record layout for the Video ViewingAnalysis File 205 which is produced by the Measurement Engine 200. Thisis the analyzed detail data which was used as input to the summarizationprocess. This provides the picture of the analyzed viewing activity dataat a session level. This data can be used for additional analysis.

Alternative Embodiments

Note that the specification and drawings and program code use certainterms interchangeably. The reader will note this most frequently withthe terms set-top box and video asset viewing device. The reader willappreciate that a set-top box is merely a specific kind of video assetviewing device. A smart phone, a tablet device, a gaming console are allexamples of video asset viewing device. Thus any reference to a set-topbox should be read to also include any kind of a video asset viewingdevice.

Although the description above contains much specificity, this shouldnot be construed as limiting the scope of the embodiments but as merelyproviding illustrations of some of several embodiments. As a nonlimitingexample, additional qualifiers may be added along with demographic andgeographic codes. Additional Histograms may be created based on othermetrics. Additional calculations can be done once the data is loaded tothe various data structures.

Scope of Viewer Interaction Data Loaded

I presently contemplate that the Measurement Engine 200 will processviewer interaction data for one Video Program at a time. Anotherembodiment may process more than one program, or only one airing of aprogram or some other combination.

Viewing Activity

I presently contemplate tracking the viewing activity (play, skip, fastforward, reverse, etc.) identified herein. Another embodiment may trackfewer kinds of viewing activity or other similar activity.

Methods for Receiving Data

I presently contemplate Playback Mode File 110, the Playback DelayPenalty Factor File 120, the Histogram Definition File 130 all beingprovided in flat files, but another embodiment may provide this data inany computer readable format including but not limited to data basetables, XML messages, or other messaging constructs.

I presently contemplate Video Program Airing File 150 data and the VideoProgram Airing Segment File 160 data being provided in flat files, butanother embodiment may provide this data in any computer readable formatincluding but not limited to data base tables, XML messages, or othermessaging constructs.

I presently contemplate Video Viewing Event File 170 data data beingprovided as a flat file, but another embodiment may provide this data inany computer readable format including but not limited to data basetables, XML messages, or other messaging constructs.

I presently contemplate that the Video Viewing Event File 170 data beingsorted as part of extracting that data from the Media Measurement DataBase 100, but another embodiment may sort this data as a separate steponce it is extracted from the Media Measurement Data Base 100.

Playback Delay Penalty

I presently contemplate one Playback Delay Penalty definition that isapplicable for all activity related to the Video Program. Anotherembodiment may specify differing playback delay penalty definitionsdepending on program type, content type, etc. As a nonlimiting example,a sports program may have one playback delay penalty definition while amovie may have a different playback delay penalty definition.

Identifiers for Data

I presently contemplate using a combination of numeric and mnemonics forthe various identifiers such as market, demographic code, geographiccode, channel call sign, video program id, video program airing id,industry program id, industry asset id, and other similar fields, butanother embodiment could use only numeric values as identifiers withlinks to reference tables for the descriptions of the numericidentifiers or only mnemonic identifiers.

Data Structure Specifications

I presently contemplate allowing multiple, up to 4, video programairings for each video program, but another embodiment may allow adifferent number of video program airings.

I presently contemplate allowing multiple, up to 20,demographic-geographic-device combinations at the various levels, butanother embodiment may allow a different number of such combinations.

I presently contemplate allowing multiple, up to 30, histogram buckets,but another embodiment may allow a different number of histogrambuckets.

I presently contemplate allowing a video program and its correspondingairings to be up to 4 hours in length (14400 seconds), but anotherembodiment may allow a shorter or longer video program durations.

I presently contemplate allowing multiple, up to 60, one minute videoprogram segments for a video program, but another embodiment may allow adifferent number of segments.

I presently contemplate each video program segment will be one minute(60 seconds) in duration, but another embodiment may allow a shorter orlonger segments.

I presently contemplate allowing multiple, up to 20, playback delaypenalty factors, but another embodiment may allow a different number ofsuch factors.

Programming Algorithm Scope

I presently contemplate executing the algorithms described hereinseparately in some sequence, but another embodiment could combinemultiple simple algorithms into fewer complex algorithms.

Receiving Date and Time Information

I presently contemplate that the various file formats which provide dateand time information will provide such data in the format indicatedwhether this be (a) a date format such as YYYY-MM-DD HH:MM:SS AM/PM, or(b) a number format identifying the second of the program, or (c) thesecond since the true beginning of the program. Another embodiment mayprovide similar values that can be used to accomplish a similar result.Nonlimiting examples include UTC time, Epoch time (seconds since Jan. 1,1970), etc. Either embodiment can be used as input to create themetrics.

I presently contemplate receiving all of the date and time values inlocal time, but another embodiment may provide these in CoordinatedUniversal Time (UTC time).

Usage of the Media Measurement Model Data Model

I presently contemplate that the video program data, video programairing data, video program airing segment data, the viewing data, andthe various supporting elements will be provided in a format similar tothat shown herein, but another embodiment may capture the viewing datain some other format and make that data available to the MeasurementEngine 200 for analysis while still working within the spirit and scopeof this disclosure.

General Information

I presently contemplate using variables having the data types and fieldsizes shown, but another embodiment may use variables with differentdata types and field sizes to accomplish a similar result.

I presently contemplate tracking viewing activity at the granularity ofone second, but another embodiment may track viewing activity at a finergranularity, perhaps half-second, or tenth-second, or millisecond. Yetanother embodiment may receive data at a granularity finer than onesecond and round to the nearest second for use by the Measurement Engine200.

I presently contemplate using Data Structures similar to those definedherein, but another embodiment may use a different Data Structure orData Structures to accomplish a similar result. As a nonlimitingexample, another embodiment may use database tables or other objectsinstead of Data Structures similar to those I have defined herein toaccomplish a similar result while still working within the spirit andscope of this disclosure.

Implementation Information

I presently contemplate using the WINDOWS 7 Professional operatingsystem from MICROSOFT Corporation, but another embodiment may use adifferent operating system.

I presently contemplate using FUJITSU® NetCOBOL® for WINDOWS® version10.1 developed by FUJITSU® and distributed by Alchemy Solutions Inc, butanother embodiment may use a different programming language or adifferent version of COBOL.

General Remarks

It will be apparent to those of ordinary skill in the art that variouschanges and modifications may be made which clearly fall within thescope of the embodiments revealed herein. In describing an embodimentillustrated in the drawings, specific terminology has been used for thesake of clarity. However, the embodiments are not intended to be limitedto the specific terms so selected, and it is to be understood that eachspecific term includes all technical equivalents which operate in asimilar manner to accomplish a similar purpose.

In general, it will be apparent to one of ordinary skill in the art thatvarious embodiments described herein, or components or parts thereof,may be implemented in many different embodiments of software, firmware,and/or hardware, or modules thereof. The software code or specializedcontrol hardware used to implement some of the present embodiments isnot limiting of the present embodiment. For example, the embodimentsdescribed hereinabove may be implemented in computer software using anysuitable computer software language type such as, for example, C, C#, orC++ using, for example, conventional or object-oriented techniques. Suchsoftware may be stored on any type of suitable computer-readable mediumor media such as, for example, a magnetic or optical storage medium.Thus, the operation and behavior of the embodiments are described inCOBOL style pseudocode purely as a matter of convenience. It is clearlyunderstood that artisans of ordinary skill would be able to designsoftware and control hardware to implement the embodiments presented inthe language of their choice based on the description herein with only areasonable effort and without undue experimentation.

The processes associated with the present embodiments may be executed byprogrammable equipment, such as computers. Software or other sets ofinstructions that may be employed to cause programmable equipment toexecute the processes may be stored in any storage device, such as, forexample, a computer system (non-volatile) memory, a compact disk, anoptical disk, magnetic tape, or magnetic disk. Furthermore, some of theprocesses may be programmed when the computer system is manufactured orvia a computer-readable medium.

It can also be appreciated that certain process aspects disclosed hereinmay be performed using instructions stored on a computer-readable memorymedium or media that direct a computer or computer system to performprocess steps. A computer-readable medium may include, for example,memory devices such as diskettes, compact discs of both read-only andread/write varieties, optical disk drives, memory sticks, and hard diskdrives. A computer-readable medium may also include memory storage thatmay be physical, virtual, permanent, temporary, semi-permanent and/orsemi-temporary.

In various embodiments disclosed herein, a single component or algorithmmay be replaced by multiple components or algorithms, and multiplecomponents or algorithms may be replaced by a single component oralgorithm, to perform a given function or functions. Except where suchsubstitution would not be operative to implement the embodimentsdisclosed herein, such substitution is within the scope presentedherein. Thus any element expressed herein as a means or a method forperforming a specified function is intended to encompass any way ofperforming that function including, for example, a combination ofelements that performs that function. Therefore, any means or methodthat can provide such functionalities may be considered equivalents tothe means or methods shown herein.

While I have developed this embodiment on a personal computer, it can beappreciated that the “data analysis computer system” may be, forexample, a wireless or wire line variety of a microcomputer,minicomputer, server, mainframe, laptop, personal data assistant (PDA),smart phone, cellular phone, cable box, pager, processor, fax machine,scanner, or any programmable device configured to transmit and receivedata over a network. Computer devices disclosed herein may includememory for storing certain software applications used in obtaining,processing and communicating data. It can be appreciated that suchmemory may be internal or external to the disclosed embodiments. Thememory may also include any means or method for storing software,including a hard disk, an optical disk, floppy disk, ROM (read onlymemory), RAM (random access memory), PROM (programmable ROM), EEPROM(electrically erasable PROM), and other computer-readable media.

While various embodiments have been described herein, it should beapparent, however, that various modifications, alterations andadaptations to those embodiments may occur to persons skilled in the artwith the attainment of some or all of the advantages described herein.The disclosed embodiments are therefore intended to include all suchmodifications, alterations and adaptations without departing from thescope and spirit of the embodiments presented herein as set forth in theappended claims.

Accordingly, the scope should be determined not by the embodimentsillustrated, but by the appended claims and their legal equivalents.

Conclusions, Ramifications, and Scope

In my previous Applications, I have identified numerous Conclusions,Ramifications, and Scope items. Many of those are similar for thisapplication. The Conclusions, Ramifications, and Scope items from myApplication U.S. application Ser. No. 12/981,301 filed on Dec. 29, 2010,and my U.S. application Ser. No. 13/052,026 filed on Mar. 18, 2011, andmy U.S. application Ser. No. 13/360,704 filed on Jan. 28, 2012 areincluded herein by reference but not admitted to be prior art.

In this discussion below, I will focus on new ramifications introducedby this Application.

From the description above, a number of advantages of some embodimentsof my Measurement Engine 200 and its supporting processes becomeevident:

In this specification I have taught how to measure Linear Viewingactivity, and Digital Video Recorder recording and viewing activity, andVideo On Demand viewing activity. Within this context, I have taught howto measure such viewing activity at multiple levels: (a) the VideoProgram Level, (b) the Video Program Airing level, and (c) the VideoProgram Airing Segment level. Within these three levels, I have taughthow to calculate metrics across the level and for each second within thelevel. Regarding the ‘across the level’ metrics, I have taught how tocalculate metrics that will provide a summary view of the viewingactivity related to the relevant level. In order to provide a deeperlook, I have also taught how to calculate metrics at a second-by-secondlevel in the video content.

All of these metrics can be loaded to a database for longitudinalanalysis. As a nonlimiting example, the program level metrics can betracked to identify week-to-week activity. Then the more detailedmetrics can provide additional insight into the causes behind theoverall trends.

By having a Measurement Engine 200 that is able to measure Linearviewing activity and DVR and VOD viewing activity, I can provide insightinto viewing patterns across these viewing modes.

Additionally, by having a Measurement Engine 200 that is able to measuresecond-by-second activity, I can provide insight into the use of trickmodes and how viewers use such modes to skip past content that is not ofinterest to them.

In the case of DVR viewing, by having the ability to discount viewing ofDVR recordings based on elapsed time since the recording, I can reflectthe reduce value of the ads as they become stale.

By having a Measurement Engine 200 that is able to measure LinearViewing activity, and Digital Video Recorder recording and viewingactivity, and Video On Demand viewing activity, I have introduced theability to measure viewing activity of various video assets withattention also being given to measuring linear viewing activity and timeshifted viewing activity. Thus I am able to accurately measure adviewership during playback of a DVR or VOD asset. I have also taught howto value that viewership based on the amount of time that has elapsedbetween the original recording of the asset and the subsequent playbackof the asset. I have also taught how to measure ad impressions which mayoccur during playback, including playback that involved a variety oftrick plays.

Additionally, I have taught how to distinguish viewing activity byvarious demographic groups, geographic areas, and devices based oncharacteristics. These measures can provide valuable insight into viewerbehavior.

The ability to produce metrics that were not previously possible willprovide information that is valuable to advertisers and contentproviders and service providers.

This method of tracking viewing activity on a second-by-second basis iscontrary to the teaching of those who work with start time and duration(seconds viewed) in a relational data base model. Thus I am able tosolve problems previously found insolvable when limited to using theexisting techniques. I am able to provide metrics that could not beproduced using existing techniques.

Subsequent Usage of the Metrics

The metrics produced by the Measurement Engine 200 readily lendthemselves to dimensional analysis using contemporary data warehousemethods. A Fact table in such an application may contain viewing datafor an video program or a video program airing or a video program airingsegment. Multiple Dimension tables can readily be envisioned by thoseskilled in the art. As non-limiting examples, various values includingdemographic group, geographic group, viewing device type, program genre,viewing date, viewing time, viewing day of week, etc. could beDimensions. Additionally, other attributes regarding the program contentcould be included in such an analysis by using the industry program idto join to other reference data that may be available to the analyst.

The metrics produced by the Measurement Engine 200 can be loaded to adata warehouse to support additional longitudinal analysis beyond whatis done by the Engine. Thus we can readily envision a myriad of uses forthe metrics produced by the Measurement Engine 200.

All of this could be done using anonymous and/or de-identifiedidentifiers for video viewing device, for household, and for viewer allto protect viewer privacy.

Numerous additional metrics can readily be identified by those skilledin the art. Additionally, numerous additional uses for the metricsidentified herein will be readily evident to those skilled in the art.

Other Ramifications

In today's world where the number of media viewing choices is vast, itis often difficult for the viewer to locate the content that he or shemight be most interested in receiving. To assist in solving thisproblem, a content provider could develop viewing profiles that couldthen be used to suggest content to a viewer. Such profiles can bedeveloped by tracking the viewing history of various groups of viewers.As an example, the Measurement Engine 200 can produce metrics whichidentify the viewing behavior of various groups of people. Perhaps avideo asset that represents a classic movie earns very high viewingrates with one group while a video asset that represents a mystery movieearns very high viewing rates with another group. Then a system could besetup to suggest candidate movies based on the viewer's viewing group sothat a viewer in the first viewing group may be presented with a list ofclassic movie titles while a viewer in the second group would bepresented with a list of mystery movies. The viewer is thus assisted inchoosing content.

SUMMARY

In accordance with one embodiment, I have disclosed acomputer-implemented method of using video asset viewing data that hasbeen loaded to a media measurement data model as input to a measurementengine which then calculates Linear, DVR, and VOD asset viewing activityat three levels: (a) Video Program, (b) Video Program Airing, (c) VideoProgram Airing Segment, where each level provides summary metrics forgroupings of Demographic Code, Geographic, and/or Device Characteristic,and also second-by-second viewing metrics within the Demographic,Geographic, Device groupings. Together these metrics provide detailedinformation on customer viewing behavior which can be used to drivebusiness decisions for service providers, advertisers, and contentproducers. Additionally, a viewing histogram file is produced. Otherembodiments can produce similar results using data from a source otherthan the media measurement data model as long as that data is properlyformatted for my Measurement Engine.

These viewing metrics meet pressing needs for detailed audienceviewership information that is not presently available and thus themetrics will be of great value to the industry.

The invention claimed is:
 1. A method comprising: determining, by acomputing system and for a segment of a plurality of segments of a videoasset, a video-viewing mode via which a first video-asset-viewing deviceoutputted the segment; determining, by the computing system, for thesegment of the plurality of segments, and based on the video-viewingmode, a first value; determining, by the computing system, for thesegment of the plurality of segments, and based on a video-viewing modevia which a second video-asset-viewing device outputted the segment, asecond value, wherein the first value is different from the secondvalue; based on determining that the video-viewing mode via which thefirst video-asset-viewing device outputted the segment corresponds toplayback of one or more segments of the video asset, adjusting, by thecomputing system, a first video viewing count, associated with thesegment, by the first value; and based on determining that thevideo-viewing mode via which the second video-asset-viewing deviceoutputted the segment corresponds to fast-forwarding one or moresegments of the video asset, adjusting, by the computing system, asecond video viewing count, associated with the segment, by the secondvalue.
 2. The method of claim 1, further comprising: determining, by thecomputing system and based on the video-viewing mode via which the firstvideo-asset-viewing device outputted the segment, a count of a number ofsegments with respect to which playback was employed by the firstvideo-asset-viewing device.
 3. The method of claim 1, wherein thedetermining the second value comprises determining a speed at which thesecond video-asset-viewing device outputted the segment of the pluralityof segments of the video asset.
 4. The method of claim 1, wherein thedetermining the video-viewing mode comprises determining an amount oftime between when the video asset was made available for output and whenthe first video-asset-viewing device outputted the segment of theplurality of segments of the video asset.
 5. The method of claim 1,further comprising: grouping, by the computing system, a plurality ofvalues based on the video-viewing mode via which the firstvideo-asset-viewing device outputted the plurality of segments and aplurality of values based on the video-viewing mode via which the secondvideo-asset-viewing device outputted the plurality of segments with aset of values associated with the video asset; and determining, by thecomputing system and based on the set of values, avideo-viewing-activity metric for the video asset.
 6. The method ofclaim 5, further comprising determining, by the computing system, thateach value in a subset of the set corresponds to one or more criteriafor the video-viewing-activity metric.
 7. The method of claim 6, whereinthe one or more criteria comprise a viewer-demographic criterion,wherein the determining that each value in the subset corresponds to theone or more criteria comprises determining that each value in the subsetcorresponds to the viewer-demographic criterion, and wherein thedetermining the video-viewing-activity metric comprises determining avideo-viewing-activity metric for the viewer-demographic criterion. 8.The method of claim 6, wherein the one or more criteria comprise ageographic criterion, wherein the determining that each value in thesubset corresponds to the one or more criteria comprises determiningthat each value in the subset corresponds to the geographic criterion,and wherein the determining the video-viewing-activity metric comprisesdetermining a video-viewing-activity metric for the geographiccriterion.
 9. A method comprising: determining, by a computing systemand for a segment of a plurality of segments of a video asset, avideo-viewing mode via which a first video-asset-viewing deviceoutputted the segment; determining, by the computing system, for thesegment of the plurality of segments, and based on the video-viewingmode, a first value; determining, by the computing system, for thesegment of the plurality of segments, and based on a video-viewing modevia which a second video-asset-viewing device outputted the segment, asecond value, wherein the first value is different from the secondvalue; based on determining that the video-viewing mode via which thefirst video-asset-viewing device outputted the segment corresponds tomuting one or more segments of the video asset, adjusting, by thecomputing system, a first video viewing count, associated with thesegment, by the first value; and based on determining that thevideo-viewing mode via which the second video-asset-viewing deviceoutputted the segment corresponds to rewinding one or more segments ofthe video asset, adjusting, by the computing system, a second videoviewing count, associated with the segment, by the second value.
 10. Themethod of claim 9, further comprising: determining, by the computingsystem and based on the video-viewing mode via which the secondvideo-asset-viewing device outputted the segment, a count of a number ofsegments with respect to which rewinding was employed by the secondvideo-asset-viewing device.
 11. The method of claim 9, wherein thedetermining the second value comprises determining a speed at which thesecond video-asset-viewing device outputted the segment of the pluralityof segments of the video asset.
 12. The method of claim 9, wherein thedetermining the video-viewing mode comprises determining an audio levelutilized by the first video-asset-viewing device with respect to thesegment of the plurality of segments of the video asset.
 13. The methodof claim 9, further comprising: determining, by the computing system,for the segment of the plurality of segments, and based on aggregatingthe first value and the second value, a third video viewing countassociated with the segment.
 14. The method of claim 13, furthercomprising: determining, by the computing system and for the segment ofthe plurality of segments of the video asset, a count of a number ofvideo-asset-viewing devices that outputted the segment of the pluralityof segments of the video asset; wherein the third video viewing countcomprises the count modified by the first value and by the second value.15. A method comprising: determining, by a computing system and for asegment of a plurality of segments of a video asset, a video-viewingmode via which a first video-asset-viewing device outputted the segment;determining, by the computing system, for the segment of the pluralityof segments, and based on the video-viewing mode, a first value;determining, by the computing system, for the segment of the pluralityof segments, and based on a video-viewing mode via which a secondvideo-asset-viewing device outputted the segment, a second value,wherein the first value is different from the second value; based ondetermining that the video-viewing mode via which the firstvideo-asset-viewing device outputted the segment corresponds torecording one or more segments of the video asset, adjusting, by thecomputing system, a first video viewing count, associated with thesegment, by the first value; and based on determining that thevideo-viewing mode via which the second video-asset-viewing deviceoutputted the segment corresponds to pausing one or more segments of thevideo asset, adjusting, by the computing system, a second video viewingcount, associated with the segment, by the second value.
 16. The methodof claim 15, further comprising: determining, by the computing systemand based on the video-viewing mode via which the firstvideo-asset-viewing device outputted the segment, a count of a number ofsegments with respect to which recording was employed by the firstvideo-asset-viewing device.
 17. The method of claim 15, wherein thedetermining the video-viewing mode comprises determining an amount oftime between when the video asset was made available for output and whenthe first video-asset-viewing device outputted the segment of theplurality of segments of the video asset.
 18. The method of claim 15,wherein the determining the video-viewing mode comprises determining thevideo-viewing mode via which the first video-asset-viewing deviceoutputted the segment during a first viewing event, the method furthercomprising: determining a second video-viewing mode via which the firstvideo-asset-viewing device outputted the segment during a second viewingevent; and adjusting, based on the second video-viewing mode, the firstvalue.
 19. The method of claim 15, further comprising: determining, bythe computing system, for the segment of the plurality of segments, andbased on aggregating the first value and the second value, a third videoviewing count associated with the segment.
 20. The method of claim 19,further comprising: determining, by the computing system and for thesegment of the plurality of segments of the video asset, a count of anumber of video-asset-viewing devices that outputted the segment of theplurality of segments of the video asset; wherein the third videoviewing count comprises the count modified by the first value and by thesecond value.